Add safe invocation CLI syntax - #375
Conversation
0824cce to
60bda03
Compare
SUch syntax is useful for projects like buildpacks and other automated CI/CD tools. It would allow these tools to very easily invoke a task if it exists, without failing if it doesn't.
60bda03 to
0c61366
Compare
|
@byroot With this change, a task whose name ends with I have rarely seen such names in real projects, so I could accept this as an incompatibility, but is that breakage intended, or do you plan to handle these cases? |
I didn't think those were valid names. If it is a concern, I can look at another symbol that isn't currently a valid name if there is one. But as you suggested, I can also look at handling the ambiguity of it. Just let me know what you prefer. |
|
Sorry for the slow reply. Let's keep |
Example:
rake may:or:maynot:exist?Such syntax is useful for projects like buildpacks and other automated CI/CD tools.
It would allow these tools to very easily invoke a taskif it exists, without failing if it doesn't.
@hsbt is this a feature that could be acceptable?
Also cc @schneems, since as maintainer of https://github.com/heroku/heroku-buildpack-ruby I suspect such feature could be useful.