Disable specific paths from linting (or disable if no config is found and certain deps are present)

[brettz9]

Issue Type

Feature Request

Issue Description

I've run into a couple projects (eslint-plugin-unicorn, licensee.js, etc.) which are not open to using the normal .eslintrc process for their linting, e.g., relying on xo or standard which apply one standard through their own means.

However, while these appear to have their own IDE tools (linter-js-standard and linter-xo and perhaps there are others out there connected to these) that can hook into Atom's linter, when I keep the linter-eslint option "Disable when no ESLint config is found (in package.json or .eslintrc)" unchecked, I get errors polluting my linter. (I like having this option enabled so I can quickly see there are errors, e.g., problems parsing const, alerting me to the fact that a project may need linting; I'm not clear on what other linting it may do if there is no config to use though.)

So, anyways, it'd be great to be able to add a list of paths that should not be checked.

Though this is not critical, it might be even better if you could accept in options a list of some dependencies/devDependencies (like xo or standard) which, if no other eslint config was found, yet these dev/dependencies were present, would cause linting messages not to be shown. (linter-js-standard has an option to only lint if a package was found locally, so a similar approach has been taken before.) Then there should be little need to manually manage paths (except to add any new dependencies that work in this way).

Thanks!