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
When JobA calls SubJobB and does not pass in ALL of the options, any options that have Default values fail to be parsed at all. Instead, they act as if the option does not exist (ie .. "@option.DRY@" really looks like "@option.DRY@"!).
The text was updated successfully, but these errors were encountered:
In scripts, missing option values are replaced with blank string (as of 1.6), however, note that Script File steps do not have an token substitution used.
I am seeing a behavior in 2.0 dev where option value that has not been set is not replaced with a blank string, so I will fix that.
However, (in 2.0) job references do get default values substituted for unset options
When JobA calls SubJobB and does not pass in ALL of the options, any options that have Default values fail to be parsed at all. Instead, they act as if the option does not exist (ie .. "@option.DRY@" really looks like "@option.DRY@"!).
The text was updated successfully, but these errors were encountered: