You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That's a good question. Code Climate doesn't yet have the functionality to ignore issues based on severity, but it looks like you can control whether warnings are emitted in ESLint with the --quiet flag:
Handling warnings --quiet
This option allows you to disable reporting on warnings. If you enable this option, only errors are reported by ESLint.
A downside is that you wouldn't see these warnings anywhere in the codeclimate.com interface, since they would cease to be emitted by the engine. Might be a good workaround for now though.
It looks like codeclimate marks new warnings in results? Is that expected? Or should it ignore those warnings? Just curious.
https://codeclimate.com/github/blimmer/test-codeclimate-eslint/issues
The text was updated successfully, but these errors were encountered: