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
for example have the following setup
program .option('-v --verbose', 'show verbose logging') program .command('release') .option('-v --version <version>', 'version of the release')
if I execute my command with
myBin release -v 1.0.0
then program.verbose = true, although i expect it to be false.
i expect it to be true when: myBin -v release (see difference in order).
myBin -v release
The text was updated successfully, but these errors were encountered:
The global options can come before or after the command, so there is a conflict between the two uses of -v.
This issue has not had any activity in over six months. It isn't likely to get acted on due to this report.
Feel free to open a new issue if it comes up again, with new information and renewed interest.
Thank you for your contributions.
Sorry, something went wrong.
Pull Request opened to add .enablePositionalOptions() and .passThroughOptions(): #1427
.enablePositionalOptions()
.passThroughOptions()
No branches or pull requests
for example have the following setup
if I execute my command with
then program.verbose = true, although i expect it to be false.
i expect it to be true when:
myBin -v release
(see difference in order).The text was updated successfully, but these errors were encountered: