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
Send warnings to STDERR, not STDOUT #2082
Labels
Comments
Good call, this should be fixed. |
docwhat
added a commit
to docwhat/website
that referenced
this issue
Dec 11, 2018
- jsx-eslint/eslint-plugin-react#2082 is just the symptom that is causing my editor to add "Warnings" to the top of my .js files. - prettier/prettier-eslint#194 is the actual bug; prettier-eslint isn't passing the `baseConfig` to eslint.
docwhat
added a commit
to docwhat/website
that referenced
this issue
Dec 12, 2018
- jsx-eslint/eslint-plugin-react#2082 is just the symptom that is causing my editor to add "Warnings" to the top of my .js files. - prettier/prettier-eslint#194 is the actual bug; prettier-eslint isn't passing the `baseConfig` to eslint.
Could there be a new release including this fix ? |
1 task
1 task
1 task
v7.12.0 is released. |
This was referenced Dec 28, 2018
Closed
This was referenced Jan 4, 2019
Closed
Closed
This was referenced Jan 13, 2019
Merged
This was referenced Sep 22, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In issue #1955 the warning is being sent to STDOUT which is messing up editors by adding the warning to the top of the file.
All warnings and errors should be sent to STDERR.
The text was updated successfully, but these errors were encountered: