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 2891 - eslint not showing errors. #2910

Merged
merged 1 commit into from
Nov 27, 2019

Conversation

hsanson
Copy link
Contributor

@hsanson hsanson commented Nov 26, 2019

ESLint errors are contained in an array that can contain different
stuff other than JSON error messages. This patch iterates over the whole
array ignoring any non-json data.

Fix #2891 for ESLint only.

ESLint errors are contained in an array that can contain different
stuff other than JSON error messages. This patch iterates over the whole
array ignoring any non-json data.
@RyanSquared
Copy link
Member

RyanSquared commented Nov 26, 2019

Assuming tests pass, LGTM.


Edit: This comment only showed up way after tests pass. LGTM.

@elebow
Copy link
Member

elebow commented Nov 26, 2019

It looks like #2909 has [the start of] a more general solution, preventing warning output from the tool.

@hsanson
Copy link
Contributor Author

hsanson commented Nov 26, 2019

This PR will ignore deprecation warnings no matter if the --no-deprecation flag is used or not when invoking the linter. Since users can change the eslint executable and options using g:ale_javascript_eslint_executable and g:ale_javascript_eslint_options the solution in #2909 may not work for some.

@w0rp w0rp merged commit d8195e9 into dense-analysis:master Nov 27, 2019
@w0rp
Copy link
Member

w0rp commented Nov 27, 2019

Cheers! 🍻

This will fix the issue.

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.

ALE does not show errors for cppcheck
4 participants