-
Notifications
You must be signed in to change notification settings - Fork 19
Conversation
As a reminder: command names are class names. That's why it does not support dash so far. |
Imo, command should have a name, a strict name. We could implement alias system and user could use them for theses cases ( |
@Hywan I think handling several names for one command is not really a good thing as you say. One thing that could be good would be to support several names based on a convention: command names are computed from the command classname. So why not splitting the name on camel-case:
|
👍 for @stephpy suggestion for an alias system and/or a fuzzy logic: |
Is easy to implement and a good thing. @jubianchi There is not at this moment a CommandRepository where we could implements a alias|fuzzy logic without browsing all classes on Hoa*_\Bin_*. |
@stephpy the fuzzy logic is the extra-thing/bonus here :) |
Fuzzy logic? +1 @jubianchi but how to do that in a single |
@Hywan fuzzy logic: http://blog.mageekbox.net/?post/2011/10/12/Docteur-Levenshtein%2C-je-pr%C3%A9sume @Hywan |
We already such an approach for ambiguous options: https://github.com/hoaproject/Console/blob/bc13787e92dc3e1eae33932a8c96ee162e08f48f/GetOption.php. It is based on I can't use Line 698 in d957a86
|
@Hywan zFormat ?! WTF ? :) |
@jubianchi Read the docs ;-). |
Ok, so I would like to use |
Still revelant ? |
Yup! See #57. But we should move this in the… |
This issue was moved to hoaproject/Cli#14 |
Done. |
We just remove dashes in command name. For example, for the
Hoa\Devtools\Bin\Requiresnapshot
command, we can write:instead of
The first one is far more readable.
Of course, we can also write:
and it will work.
Pro: help to read long commands.
Con: several “names” for the same command, which is not… good :-/.
Thoughts?
/cc @hoaproject/hoackers