-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
9.1.0 - option.conflicts not working #1710
Comments
Thanks for the example. This is a bug. When a subcommand is used, the conflicts are only being checked on the subcommand and not the program. (In the code it looks right with |
Any idea when this might be released? |
Hi @rpearce63 , likely within a week. (Not a hard rule, but I prefer to wait a month between releases.) |
Fixed in Commander v9.2.0 |
The update worked. Thanks.
|
I'm trying to use the option conflicts configuration, but it doesn't appear to catch the conflicts.
When I run with:
node commands.js claim -a -x OG
The result is:
claim with options {"all":true,"exact":"OG"}
Have I configured it incorrectly? Also tried specifying just the short names. Same result.
Thanks.
The text was updated successfully, but these errors were encountered: