Task schema generation should understand and use aliases

Question

Task schema generation should understand and use aliases

vtbassmatt opened this issue 6 years ago · 2 comments

task.json offers an ability for inputs to be aliased. Typically the aliases are newer / corrected forms, and we should use those instead of the raw variable names where available.

Answer 1 · 2018-12-06T09:26:43.000Z

Possibly the tip could also suggest using the non-alias version.

Answer 2 · 2018-12-06T14:11:33.000Z

Because of history, the alias is often the nicer string for YAML. Inputs were originally hidden from the end user, so many tasks were fairly free-form with what they were called. The end user only saw the display name. Now that they're directly exposed, we don't want to break people using the "real" name but we did want a way to offer up a nicer string.