feat: adding yargs-parser functionality #1
Conversation
This file contains hidden or 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
commented
Feb 1, 2022
bcoe
commented
Feb 1, 2022
bcoe
commented
Feb 6, 2022
|
|
||
| it('should set the value of the final option in a group to the next supplied value', function () { | ||
| const parse = parser(['-cats', 'meow'], { | ||
| withValue: ['s'] |
There was a problem hiding this comment.
Most significant API change so far, is that we must set withValue for any arguments that expect a value.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Working on porting as much of yargs-parser's functionality to using parseArgs as makes sense.