You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While writing a task file, I wanted to have a variable A having a value depending on the value of another B that could be passed by the user when calling the task.
I wanted to have a third variable C to use to use the resulting value of A.
The whole taskfile is then imported in another one.
What happened?
Depending on the position of B in the command line, C would be evaluated twice with two different values of A.
This only occurs if the first example.
What did I do?
While writing a task file, I wanted to have a variable
A
having a value depending on the value of anotherB
that could be passed by the user when calling the task.I wanted to have a third variable
C
to use to use the resulting value ofA
.The whole taskfile is then imported in another one.
What happened?
Depending on the position of
B
in the command line,C
would be evaluated twice with two different values ofA
.This only occurs if the first example.
First example:
included.yml
task.yml
Execution:
Second example:
include.yml stays the same.
taskfile.yml
Execution:
Expectated behavior
I would expect the dynamic variable to be executed once in every case.
Version
3.41
Operating system
Linux lima-vpp3 5.15.0-130-generic #140-Ubuntu SMP Wed Dec 18 17:59:36 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux
Experiments Enabled
With and without
TASK_X_MAP_VARIABLES=1
The text was updated successfully, but these errors were encountered: