-
Notifications
You must be signed in to change notification settings - Fork 290
Verb aliases #90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This can be trivially fixed in the short term by setting |
@kirillkovalenko, this is a nice idea! 👍 Thansk! |
@nemec, an example? |
@gsscoder are you really back? the issue is almost 2 y.o. now. |
@kirillkovalenko, check the project activity this is the state of art of Command Line Parser Library 2.0.x-alpha: https://github.com/gsscoder/commandline/wiki/Latest-Version |
There could be even more sugar. Many tools allow using a shorter form of a verb or command (e.g. 'hg o' instead of 'hg out') provided that this shorter form is not ambiguous, and if it is ambiguous a nice hint is provided in the error message, e.g. 'hg: command 'a' is ambiguous: add addremove annotate archive' |
@kirillkovalenko, this alias is implicit like: [Verb("add")] class AddOptions { }
[Verb("commit")] class CommitOptions { } Will allow [Verb("add", Alias=new[] {"a"})] class AddOptions { }
[Verb("commit", Alias=new[] {"cm", "cmt"})] class CommitOptions { } ? |
👍 from me for this feature. I could use verb aliases in my current project, if they were available. |
@gsscoder what I meant was allowing the following:
|
I suggest implementing verb aliases. For example: hg rename, hg move, hg mv is the same command.
The text was updated successfully, but these errors were encountered: