Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(web-scripts): positional args were being stripped out #372

Merged
merged 2 commits into from May 21, 2020

Conversation

fastfrwrd
Copy link

@fastfrwrd fastfrwrd commented May 20, 2020

the best test case for this is web-scripts test filename, which currently doesn't work.

positional args were not making there way through to the web-scripts commands, because commander 5 changed how we need to handle args. there is now conveniently an args array on the command which contains all args (positional or flagged) in order, which seems to be more reliably correct from what the user inputs compared to using the parseOptions(process.argv) method.

positional args were not making there way through to the web-scripts commands, because commander 5
changed how we need to handle args. there is now conveniently an `args` array on the command which
contains all args (positional or flagged) in order, which seems to be more reliably correct from
what the user inputs compared to using the parseOptions(process.argv) method.
@fastfrwrd
Copy link
Author

fastfrwrd commented May 20, 2020

@pmowrer, we found another issue that was introduced by tj/commander.js#1138, but I think this should solve both now.

@fastfrwrd fastfrwrd merged commit e1af1bf into master May 21, 2020
@fastfrwrd fastfrwrd deleted the fix-positional-arg-issue branch May 27, 2020 17:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants