-
Notifications
You must be signed in to change notification settings - Fork 481
Can a verb have a child verb? #35
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
Hi @sgrassie, thank you again for being there. Starting from easy things... 2.0+ documentation is condensed in this part of the wiki. Command Line never supported nested verb (nor previous stable), but it's a very interesting. We can introduce a property to set the parent verb: [Verb("verb1")]
class VerbOptions1 { }
[Verb("verbchild1", Parent="verb1")]
class VerbChildOptions1 { } Than all options classes will be normally passed to |
I am also looking for something like this, this may be useful. +1. |
Given the way verbs are defined now, out of band, this may be difficult to implement. It may be possible to recursively call choose with the remaining arguments (after excluding the first matched verb) and incorporate @gsscoder's suggestion of a |
Ok thanks, I understand. As of now, my alternative is to create more verb commands, instead of nested ones. |
Crazy idea, what if the verb name contained a space? Would that be able to fake a hierarchy? |
Isn't this the same as #13? maybe close as a duplicate? |
Dupl #13 |
Friday Jul 17, 2015 at 10:56 GMT
Originally opened as gsscoder/commandline#201
I'd like to allow the following scenarios:
Where
-u
and-z
are both specific to the respective child verbs. Is the documentation in the wiki for this still valid, or has it changed in 2.0+?The text was updated successfully, but these errors were encountered: