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
{{ message }}
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.
If there is no .jscsrc file, there is no need to run jscs linter and If there is no .jshint file, there is no need to run jshint linter etc
The text was updated successfully, but these errors were encountered:
iamstarkov
changed the title
Doesn't run custom linter if there is no custom config file for it.
Please do not run custom linter if there is no custom config file for it.
Dec 24, 2014
Hello @matmuchrapna, for linter-eslint there is now an option for disabling the plugin if there is no .elsintrc file found in the directory tree above the linted file. This option has been added to answer issue #20, which seems to be the same as this one. Did you try to enable this option ?
What do you think about setting this option to true, by default? or even get rid off it?
I found that everybody have it's own eslint configs, that's why it is unexpected behaviour to run atom-eslint with one predefined config for all plugin consumers. What do you think about it? If feature is welcomed, I will make pr.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If there is no .jscsrc file, there is no need to run jscs linter and If there is no .jshint file, there is no need to run jshint linter etc
The text was updated successfully, but these errors were encountered: