We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://web.archive.org/web/20201110211135/https://github.com/substack/subarg/issues/7
filed by @fiberthrone
I've realized that in cases like the one below unclosed contexts are just ignored by subarg without any error: subarg(['abc', '[', 'cde']) // returns { _: [ 'abc' ] } This may cause unexpected behavior. For example, this is a usual browserify (which uses subarg) run: browserify app.jsx -t [ babelify --presets [ react es2015 ] ] However, the command below will just ignore everything after the -t arg, because double brackets close a context only once. browserify app.jsx -t [ babelify --presets [ react es2015 ]] Should subarg inform of an error in some way in such cases?
I've realized that in cases like the one below unclosed contexts are just ignored by subarg without any error:
subarg
subarg(['abc', '[', 'cde']) // returns { _: [ 'abc' ] }
This may cause unexpected behavior. For example, this is a usual browserify (which uses subarg) run:
browserify app.jsx -t [ babelify --presets [ react es2015 ] ]
However, the command below will just ignore everything after the -t arg, because double brackets close a context only once.
-t
browserify app.jsx -t [ babelify --presets [ react es2015 ]]
Should subarg inform of an error in some way in such cases?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
https://web.archive.org/web/20201110211135/https://github.com/substack/subarg/issues/7
filed by @fiberthrone
The text was updated successfully, but these errors were encountered: