Skip to content
This repository has been archived by the owner on Apr 8, 2019. It is now read-only.

Allow configuration option for disabling linting for specific file names #25

Closed
damien opened this issue Mar 19, 2014 · 2 comments
Closed

Comments

@damien
Copy link

damien commented Mar 19, 2014

First off, thanks for making atom-lint! Great resource and makes it easy to use my preferred linters.

Back on topic: I'd be great to have a configuration option to disable linting for specific file types/names/extensions.

My use case: I have Rubocop enabled and it's trying to lint a large schema.rb file. This, as expected, is VERY slow and tends to lock up the UI in Atom. I don't manually edit my schema file, but I use it as a reference and atom-lint seems to run rubocop against it regardless of weather or not I actually edit the file.

My workaround for now is just temporarily disabling linting while I have such files open, but it'd be nice if I could configure atom-lint to do that for me.

@yujinakayama
Copy link
Owner

You're welcome. :)

About the specific file exclusion feature, ideally I think it should be done in each linter (as proposed in rubocop/rubocop#893) so that you don't need to specify same patterns in both .rubocop.yml and atom-lint's configuration.

That said, not all linters support the feature (currently also RuboCop doesn't) and there would be some special cases where you want exclude arbitrary files only in Atom.

So yes, I'm going to add this feature to atom-lint.

@damien
Copy link
Author

damien commented Mar 24, 2014

You, sir, are a gentleman and a scholar. Thank you very much for patching this!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants