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
In #2342 there was discussion of an alternative use-case for aliases where aliases were being used as the "main" descriptive name for the recipe and the recipe name was meant for internal use. Looking through the reasoning in #1725 and the discussion in #1302, it seems to me this use-case appeared due to a possible bug?
Given this Justfile, test1 will give the expected results while test2 will throw an error because FLAGS is parsed as a variable and evaluated to a single string 123 456 789 which cases only the $1 positional argument to be set.
Is this a desirable/intended behavior? Or should dependency arguments that are variables for a variadic parameter get split back into individual strings before getting passed to the dependent recipe?
The text was updated successfully, but these errors were encountered:
In #2342 there was discussion of an alternative use-case for aliases where aliases were being used as the "main" descriptive name for the recipe and the recipe name was meant for internal use. Looking through the reasoning in #1725 and the discussion in #1302, it seems to me this use-case appeared due to a possible bug?
Given this Justfile,
test1
will give the expected results whiletest2
will throw an error becauseFLAGS
is parsed as a variable and evaluated to a single string123 456 789
which cases only the$1
positional argument to be set.Is this a desirable/intended behavior? Or should dependency arguments that are variables for a variadic parameter get split back into individual strings before getting passed to the dependent recipe?
The text was updated successfully, but these errors were encountered: