-
-
Notifications
You must be signed in to change notification settings - Fork 422
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
Support commands which throw error on --
argument
#195
Closed
Comments
FYI: Hoping this gets addressed in facebook/flow#4189 However this should still be fixed in |
okonet
pushed a commit
that referenced
this issue
Jun 18, 2017
Closes #195 BREAKING CHANGE: This might affect existing setups which depend on the `--` argument.
Did that last PR fix this issue? It doesn't seem so to me. I still experience problems with flow :) |
This was referenced Oct 19, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using certain tools (e.g. Flow v0.48.0:
flow focus-check
) will not run correctly if they don't understand/expect an argument--
.Steps to reproduce
git init
npm init -y
yarn add lint-staged [email protected]
flow init
.lintstagedrc
:index.js
:// @flow
git add .
lint-staged
Actual result
The
flow focus-check
command will fail vialint-staged
Expected result
The
flow focus-check
command should pass, like it does when being run externally like:flow focus-check index.js
The text was updated successfully, but these errors were encountered: