extend eslint:all to include plugins

The version of ESLint you are using.

6.5.1

The problem you want to solve.

This is a followup to https://github.com/eslint/eslint/issues/6240 and https://github.com/eslint/eslint/pull/6248. The eslint:all configuration has been working great on our projects. However, some plugins implement a similar all configuration and some don’t. It’s a pain for every plugin maintainer to have to implement a similar rule, and in some cases they are unwilling to implement it. We would like to be able to enable all ESLint rules across all of our plugins by default, then configure them away from the defaults where appropriate. A couple of my previous comments for way more context:

https://github.com/eslint/eslint/issues/6240#issuecomment-221123719 https://github.com/eslint/eslint/issues/6240#issuecomment-223716227

Your take on the correct solution to problem.

ESLint should have an option to enable all rules across plugins, not just the built in rules.

Are you willing to submit a pull request to implement this change?

I’m happy to implement something like this with guidance. I implemented the eslint:all rule, but it looks like plugin rules are loaded separately from builtin rules, so it might be somewhat more complicated to implement.

[platinumazure]

I’ve thought about it some more, and I think I’m also slightly opposed on cost/benefit grounds.

I’m wary of more support questions that might come in because someone is using the ESLint core “enable all rules from a plugin”, even though 99% of those questions should go to the plugin owner. The benefit of this change does not justify the maintenance/support cost, in my view.

[kaicataldo]

I don’t really see the value in this (the benefits don’t seem to outweigh the increased confusion/support we might have to offer users), but if other members of the team are for it, I’ll defer to consensus.

I’ve removed my 👎.