-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Add mut_group
to Command
#5038
Comments
I feel like the first discussion to be having is about conflicts and |
You mean by added a dedicated issue with a minimal working example? Or I am misusing something? |
That'd work, thanks! |
here is the accompanying issue #5041 |
I would like to reiterate that this would be really nice to have. My use case is that I want to use the derive API, but I want a specific |
Please complete the following tasks
Clap Version
4.3.12
Describe your use case
I use a
Command
object that has been defined in another crate. This command has a group defined this way:I modify this object in my crate to add some additional arguments and especially this one (I do not want to relly on the default implementation of version) :
both
exclusive
andconflicts_with_all
and seems to be ignored, so as a workaround I have temporarily modified theCommand
definition in the other crate (so it does not fit the need of this initial crateDescribe the solution you'd like
Clap already has mut_arg and mut_subcommand.
It would be nice to add
mut_group
to be consistent.The solution to my problem would not require anymore to modify the former crate; only to code something similar to
I would say that the implementation of
mut_group
would be close toAlternatives, if applicable
No response
Additional Context
For sure, this
mut_group
is of interest as it is missing from the library. But I wonder if in my use case it is just a workaround around a bug in the management of conflicting argumentsThe text was updated successfully, but these errors were encountered: