Add enable
setting for ability to do project-specific disabling
#26
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I sometimes make contributions to projects which have very opinionated, noisy, or outdated ESLint configs. Sometimes they have silly ESLint plugins that I don't want to install. Sometimes I'm running
pulsar-ide-typescript-alpha
and the linting I'm getting fromtypescript-language-server
is more than enough.These are all scenarios in which I'd want a quick way to disable linting on an entire project (even when it's set up for ESLint) without disabling the package altogether. With an explicit Enable option, I can easily configure a project-specific override with
project-config
/atomic-management
or by adding"enable": false
to a.linter-eslint
file.