Wes McNamee

Ya I may just alias the fields.

With ENV Vars it's more complicated. If you look at Make, there are several rules for setting an an environment variable value. https://www.gnu.org/software/make/manual/html_node/Setting.html#Setting This functionality is something I sorely miss....

@natefinch how would you feel about just removing this line for now? since it potentially also is a security concern, as it might print secrets to the console via cmd...

some more information on this: ```yaml version: '3' tasks: # works foo: cmds: - echo '{{`${{blahblah}}`}}' # works foo2: vars: MYFOO: '{{`${{blahblah}}`}}' cmds: - echo '{{.MYFOO}}' # fails foo3: cmds:...

Definitely think that's a bug.

Yes, a bypass option would work, but escaping also would work. Bypass in this case wouldn't work well, because it prevents any sort of default behavior.

I don't agree with this being an improvement. I think this would result in more confusion, especially given the precedent that no other tool combines cmd lists into a single...

@tylermmorton what I would like to understand in greater clarity is the use case that is solved by combining the separate commands into a single script, that a multiline yaml...

@tylermmorton ok, sounds good. Ya, try the `dotenv` functionality described here: https://taskfile.dev/#/usage?id=env-files And if you run into a situation that isn't working, please open a new issue here.

I'm not totally sure what's going on in V3 here. My plan in v4 is to lazily evaluate variables. Essentially waiting until they are _used_ before discovering (and caching) the...