We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We had this problem in mochajs/mocha#1296.
The below works great:
.option('-c, --colors', 'force enabling of colors') .option('-C, --no-colors', 'force disabling of colors')
In the example below, --no-colors does not work:
--no-colors
.option('-C, --no-colors', 'force disabling of colors') .option('-c, --colors', 'force enabling of colors')
The text was updated successfully, but these errors were encountered:
I found this problem too, and I think treated the common used word no as a key work is not proper enough. We can improve it.
no
Sorry, something went wrong.
Would like this option, there are plenty of valid reasons for wanting to do this.
At the very least, please make it clear in the docs that --no won't work, thanks
--no
Closing in favour of #108
No branches or pull requests
We had this problem in mochajs/mocha#1296.
The below works great:
In the example below,
--no-colors
does not work:The text was updated successfully, but these errors were encountered: