fix: handling of one char alias as a camelCase #139
Merged
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.
Hi, thank you for a great library :).
I'm using
yargs-parser
in a lot projects, one of them is redrun (CLI tool to run multiple npm-scripts fast). It has a couple 1 char aliases:After updating to v11.0.0 some of my tests has failed, here is parsing:
And result:
the reason was
yargs-parser
handledp
the same asP
andparallel-calm
, but it isparallel
, actually.The bug is located in condition of extendAliases function:
Which is not makes check of the length of an
x
, so single char became acamelCase
so I added such check.