use YAML instead of $ prefix for dynamic variables? about task HOT 7 CLOSED

Taskfile_{{.GOOS}}.yml should be very simple.

About interpolation with same-context variables, I don't how to implement that. Maybe a list as @smyrman suggested, but seems a bit counter-intuitive to the user.

from task.

I agree with this proposal.

It also optionally allows for later features, like allowing an "env" section to be passed in (not suggesting that we do that now), or allowing shell commands as dependencies.

from task.

If the following Taskvars.yaml would save me a lot of boilerplate:

VAR1: hello
VAR2: {{.VAR1}} world #<- VAR2 would be hello world

This is probably not easly possible.

Also: Taskvars_{GOOS}.yaml would be cool to overwrite dynamic variables.

from task.

@zbindenren, I don't see that as relevant to this issue. You can create a new issue for it perhaps, but as you say, it's not really easily possible to do this in a deterministic way.

Issue #40 is more closely related to what you ask.

UPDATE: I guess it's somewhat related, in that while changing the syntax anyway, if variables where changed to be a list of objects, then it would be possible.

vars:
  - VAR1: hello
  - VAR2: "{{.VAR1}} world"
  - {VAR3: "hey", VAR4: "{{.VAR1}} there"} # Also possible, but here VAR4 may not use VAR3...
 

But probably still best discussed in a new issue.

from task.

Maybe a list as @smyrman suggested, but seems a bit counter-intuitive to the user.

I agree to that. It's not a good solution.

from task.

@zbindenren Taskvars_{{GOOS}}.yml should be working on master branch.

from task.

Great thx :-)

from task.