feat req: --flag arguments support under .CLI.ARGS

[ShubhamTiwary914]

Description

Context

Passing CLI args is possible by (ref - Forwarding CLI arguments to commands ):

tasks:
  yarn:
    cmds:
      - yarn {{.CLI_ARGS}}

and called as: task yarn -- install

But there's no flag support, requiring a lot of times to hardcode as env within taskfile, or using positional arguments and mapping the flags to position within the CLI args, for example:

tasks:
  somecommand:
    cmds:
      - |
        set -- {{.CLI_ARGS}}
        arg1=$1
        arg2=$2
        echo command --flag1 "$arg1" --flag2 "$arg2" 

---

What can be added

Adding options under the special .CLI.ARGS variable, so something the use can be something as follows:

tasks:
  somecommand:
    cmds:
        - echo command --flag1 {{.CLI.ARGS.flag1}} --flag2 {{.CLI.ARGS.flag1}}

Makes the param passing for calling commands with multiple flags much better, not having to deal with postional args splitting, or calling scripts to deal with this logic everytime.

[trulede]

@ShubhamTiwary914 You can use {{index .CLI_ARGS_LIST 0}} which will do what you want (that example gets the first flag).

[ShubhamTiwary914]

my bad I had forgotten about this issue,
@trulede true that does work yes, but it's the same positional argument thing, having to refer to the ith flag in exact order.

The workaround I found earlier, but it wasn't explicitly mentioned in the docs, only similar thing was the CLI args forwarding sections.

that is just pass not as cli args like: task command -- <cli-args-list> but directly as part of command:

version: '3'

tasks:
  demo:
    cmds:
      - echo "{{.flag_x}} {{.flag_y}}" 

and run like:

task demo flag_x=world flag_y=hello

and order doesn't matter, so I don't have to deal with splitting the args and running another filter task for this.

don't know if it is a big issue to add in docs (it was a bit annoying for me), but can be added after the cli args forwarding section in docs if anyone else has had similar issue.