Sindre Røkenes Myren 31faf05c3a Reintroduce template evaluation in variables ... With a recent commit, template evaluation for variables in tasks got broken. This reindroudces temmplate evaluation in taks, and resolves a series of issues that where previouisly present on master, such as: - Taskvars did not get evaluated as templates. - Taskvars would, in contrast to the documentation, _override_ task variables for the taks called directly via `Executor.Run(args ...string)`. This caused different behaviour in the "default" task v.s. other tasks. This commit ensures: - Priority order for variables is now according to the documentation, also for the "default" task. - Variables gets resolved in a particular order to ensure logical access to varaibles on template compile time, and that template compilation finds place _before_ resolution of dynamic variables. This change also allows the following to work: task: vars: A: "52" B: "{{.A}}" However, the following will always replace C with the uncompiled `{{.A}}`: task: vars: A: "52" C: "{{.B}}" B: "{{.A}}" Several tests have also been added to prevent this feature from breaking again. This should hopefully finally resolve issue #40.		2017-07-22 00:50:23 +02:00
..
.gitignore	add custom Cmd and Dep types	2017-07-03 21:04:38 -03:00
Taskfile.yml	Reintroduce template evaluation in variables	2017-07-22 00:50:23 +02:00
Taskvars.yml	Reintroduce template evaluation in variables	2017-07-22 00:50:23 +02:00