-
Notifications
You must be signed in to change notification settings - Fork 52
Normalize command names #143
Comments
I don't agree with this. All commands should be usable, and seeing as people will forget if it's number:list or numbers:list, it's useful for both to exist. |
As a comparison, Heroku is strict about this and it's a good CLI.`
vs.
|
@leggetter sure, so the 2 options are to either support multiple commands for one action, or to be strict and have decent fallback. We've gone the former way so far and we shouldn't drop it without understanding why it's there. I'm all open to the latter option, but this means adding some graceful fallback for these kind of typos, as well as bumping the major version for removing so much backwards compatibility. |
Agreed. To be clear: Reason for this issue are:
It could be that we were just unlucky with the recent For a workaround we could potentially just create our own helper function wrapper. |
@AlexLakatos just wanted to apologise for possibly being short and grumpy, no such thing was intended. I was at a conference abroad and answering quickly and to the point and I just realised I might have sounded a bit rude. I totally love that someone is trying to improve things, and all I wanted to do was provide some background. |
The original spec had It might make the code more complex but it makes the product more usable IMO |
This is a meta issue, tracking conventions for the CLI
:list
to the default single word commandThe text was updated successfully, but these errors were encountered: