Skip to content
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.

Please do not run custom linter if there is no custom config file for it. #25

Closed
iamstarkov opened this issue Dec 24, 2014 · 3 comments
Closed

Comments

@iamstarkov
Copy link

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

@iamstarkov 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
@jfaissolle
Copy link
Member

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 ?

@iamstarkov
Copy link
Author

Thank you, it is what I need

@iamstarkov
Copy link
Author

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants