Simplify rustup configuration by also allowing a `component:`
epage opened this issue · 3 comments
To be general, we accept components: [] but most of the time, only one component is provided and this is extra verbose.
We could simplify this by also accepting a component: rustfmt. The default would be "" and if its blank, we skip it.
If the cost of adding and maintaining the feature is essentially nil, then it seems logical to add, but I'm not sure what the expected behavior would be if one specified components and component (and how to code that logic into a template (a potential scenario where a task outshines a template 😆 )). IMO, I don't find components: [rustfmt] too egregious to write over component: rustfmt (three additional characters)
Oh, does yaml allow bare words in []?
The trivial solution is to allow specifying component and components and all get installed. I think this would be enough of a corner case that we don't need to go out of our way for it.
This has been fixed for a while 😅