fix: populate positionals when unknown-options-as-args is set #1508
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bcoe
deleted the
fix/1444-positional-not-set-with-unknown-options-as-args
branch
|
@mleguen great work 👍 |
|
Would it be possible to release this? Thanks ahead of time! |
|
@kellyselden sorry for the slow turnaround, mind taking this for a spin? Fun fact, |
This was referenced Nov 25, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Positionals where no longer populated using
unknown-options-as-args, as yargs turned them into options before handing them to yargs, but withoud declaring the corresponding option. So they were handled by yargs-parser as unknown options.The "hidden" options for the positionals are now declared when using
unknown-options-as-args.Closes #1444.