fix getRemainingFlags for arguments with multiple '--' in them#2175
Merged
kamilmysliwiec merged 1 commit intonestjs:masterfrom Jul 17, 2023
Merged
fix getRemainingFlags for arguments with multiple '--' in them#2175kamilmysliwiec merged 1 commit intonestjs:masterfrom
kamilmysliwiec merged 1 commit intonestjs:masterfrom
Conversation
micalevisk
approved these changes
Jul 15, 2023
Member
|
LGTM |
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
nest start --exec "node --experimental-specifier-resolution=node --no-warnings" --debugfails withTypeError: Cannot read properties of undefined (reading 'toUpperCase'), because thecamelCasefunction gets"de experimental-specifier-resolution=node --no-warnings"as input. splitting--will result in an empty string, and''[0]is undefined.What is the new behavior?
It doesn't break.
Does this PR introduce a breaking change?
Other information
Alternatives might be to skip all
itemvalues that don't start with '--' or that contain spaces or something. But I figured changing it to/--/gis the smallest change and has the least chance of breaking stuff that I'm not aware of.To avoid this error, either remove
--no-warningsor move--exec ...to the end.Doesn't affect version 9.1.3, affects 9.5.0