feat: support for loops with generates

[sedyh]

Hello. When I encountered that Task doesn't have fingerprinting for generated files, I started looking for workarounds by using status: test -f for each item in the generated list and suddenly realized that I can't just automate these type of checks because I can't loop over generated. The idea is to extend pr-1541: looping over dependencies with one more value.

This PR is for:

• Adding generates value with for in cmds and deps.

There will be a second PR for:

• Allowing regular cmds to run inside status for programmatic checks automation.

My workaround for checking generated files, that I want to run with this PR:

version: '3'

tasks:
  gen:
    sources:
      - protocol/**/*.proto
    generates:
      - pkg/protocol/**/*.pb.go
    status:
      - for: generates
        cmd: test -f {{.ITEM}}
    cmds:
      - buf generate

Original problem with the missing checks for generated files:

ls pkg/protocol
core  google

task gen       
task: Task "gen" is up to date

task clean     
task: [clean] rm -rf pkg/protocol/core

ls pkg/protocol
google

task gen       
task: Task "gen" is up to date # <<< must run again

version: '3'

tasks:
  gen:
    sources:
      - protocol/**/*
    generates:
      - pkg/protocol/**/*
    cmds:
      - mkdir -p pkg/protocol/google
      - touch pkg/protocol/google/important.pb.go
      - mkdir -p pkg/protocol/core
      - touch pkg/protocol/core/important.pb.go
  clean:
    cmds:
      - rm -rf pkg/protocol/core
  make:
    cmds:
      - mkdir -p protocol/google
      - touch protocol/google/important.proto
      - mkdir -p protocol/core
      - touch protocol/core/important.proto

[pd93]

Looking good so far. If willing, could you please add this change to the schema reference and usage doc. We can probably combine the sections on looping over sources/generates rather than having separate ones.

[vmaerten]

Sounds good ! Can you update the schema.json in order to add this new property ?
It's under for_attribute

[sedyh]

Sounds good ! Can you update the schema.json in order to add this new property ? It's under for_attribute

Yeah, sure. I've updated the enum values.

[vmaerten]

Thanks!

[pd93]

Thanks @sedyh 🚀

[pd93]

FYI, made some changes to the docs in 669bf33.