Provide means for disabling all rules from a given plugin within a file

I’ve been using the eslint angular plugin which works great, but some of my files aren’t angular ones which causes it to get conffused, it would be great if I could disable all rules associated with it within a given file using something like this:

/*eslint "angular/*": 0*/

[atoiv]

At the moment, I don’t see any easy way to accomplish what you want.

Is this still the case?

Another use case where disabling all rules of a plugin would help is with external eslint-configs that use multiple plugins and provide rule configurations for these plugins.

Sometimes there’s a lot of plugins used in a single eslint-config. For a specific project, it’s possible that one of the plugins is either problematic, or just not useful, and would need to be disabled.

Example use case:

Popular config eslint-config-airbnb uses, among other plugins, the magnificent accessibility plugin eslint-plugin-jsx-a11y. Even though eslint-plugin-jsx-a11y is a real gem when creating sites facing the world wide web, it is no use in a closed environment, such as electron, where aria rules are not supported. As the generated dom is only read with a single non-aria-supporting program, enforcing rules for aria is no use, and only amounts to a lot of unnecessary work and code.

The workaround that we have taken is to add an extra config file, which disables all eslint-plugin-jsx-a11y rules, into our own eslint-config repo. The problem here is, we need to keep our own config file for disabling eslint-plugin-jsx-a11y updated with all the breaking changes to eslint-plugin-jsx-a11y, in versions that eslint-config-airbnb might want to support.

While this is doable, the proposed solution in this issue, or a similar core eslint solution, would be far easier and safer alternative.

[mblodorn]

@atoiv could you please share this file?