fix: flags without an alias incorrectly reported as unknown in strict mode#30
Closed
xxiaoxiong wants to merge 1 commit into
Closed
fix: flags without an alias incorrectly reported as unknown in strict mode#30xxiaoxiong wants to merge 1 commit into
xxiaoxiong wants to merge 1 commit into
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
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.
Summary
Fixes strict mode (
unknowncallback) incorrectly reporting flags that have no alias as "unknown" when they are listed instringorbooleanoptions.Changes
src/index.js: Extendedkeysarray to includeopts.booleanandopts.stringentries alongside alias keysWhy
In strict mode,
keyswas built only fromopts.aliasentries. A flag like--barlisted instring: ['bar']with no corresponding alias would be rejected as unknown, even though it's a valid recognized flag.Repro:
Closes #27