-
-
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
Conflicting arguments in group only work for first group in YAML file #2409
Comments
Need the command which is failing and the debug output. |
Basically, the "actual behaviour" sections need actual command runs and their outputs. |
I updated the section for expected and actual behaviour. Although I must add I'm not sure what you mean by failing commands and debug output. My issue is precisely that there is no failing command when I expected it so there's no debug output I can post. |
What you wrote now is good. |
@DocKDE Can you please try with the latest master now? |
We have decided to deprecate the YAML API. For more details, see #3087. If there is interest in a YAML API, it will likely be broken out into a |
Please complete the following tasks
Rust Version
1.50.0
Clap Version
3.0.0-beta.2
Minimal reproducible code
Steps to reproduce the bug with the above code
Use this .yaml for any command line parsing.
Actual Behaviour
When calling the binary like
pdbman -QY
it fails witherror: The argument '--query' cannot be used with '--analyze'
. However the same is not true if I call multiple arguments from other groups like so:pdbman -Aqo
orpdbman -Qrt
. These commands run without error. It appears that only the args from the topmost group in the YAML file are recognized as being mutally exclusive. I verified this by changing their order.Expected Behaviour
I would expect a command calling arguments from the same group to also fail with this:
error: The argument '--residues' cannot be used with '--atoms'
if they belong to the same group.Additional Context
No response
Debug Output
No response
The text was updated successfully, but these errors were encountered: