Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Completions should suggest --no-* flags when appropriate #1431

Closed
cspotcode opened this issue Sep 26, 2019 · 0 comments · Fixed by #1509
Closed

Completions should suggest --no-* flags when appropriate #1431

cspotcode opened this issue Sep 26, 2019 · 0 comments · Fixed by #1509
Labels
feature request

Comments

@cspotcode
Copy link
Contributor

cspotcode commented Sep 26, 2019 •
edited

When a boolean flag defaults to true, I pass --no-foo to set it to false.

yargs tab-completions should propose the --no-foo flag when:

a) default for the flag is true
b) the yargs parser is configured to allow --no-* variants for boolean flags.

EDIT fixed a typo that I had backwards
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(completion): takes negated flags into account when boolean-negation is set yargs/yargs
2 participants
@bcoe @cspotcode