simplify setKey logic for yargs-parser 75 #1
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
make compatible with Node 0.10 get back to 100% test coverage
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.
Also removed arrow function to maintain compatibility with Node 0.10 (we're aiming to drop Node 0.10 support in early 2017).
Dropping the unnecessary
throw new Error('this should not happen')statements also gets this back to 100% test coverage.If you don't see any problems with this, let's "Rebase and merge" this into your branch, and then we should be able to "Squash and merge" yargs#75.
Thanks for the new tests and working through this messy logic!