Configuration to enable all rules
See original GitHub issueI would love to have a configuration that enables all rules, that way I can selectively disable them:
extends: ['eslint:all']
This way I can easily be made aware of new rules when I upgrade, and don’t have to go hunting through the docs to figure out which ones to add to my configuration file.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:13
- Comments:29 (25 by maintainers)
Top Results From Across the Web
Managing AWS Config Rules Across All Accounts in Your ...
AWS Config allows you to manage AWS Config rules across all AWS accounts within an organization. You can: Centrally create, update, and delete...
Read more >Rules - ESLint - Pluggable JavaScript Linter
A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
Read more >Configure code analysis rules - .NET - Microsoft Learn
The following table shows the different rule severities that you can configure for all analyzer rules, including code quality and code style ...
Read more >Lesson 5 How to Enable and Disable Rules and Rule Sets
These steps use Enable and Disable commands on the Rule Set screen to enable or disable all the rules in a rule set....
Read more >Best practices for firewall rules configuration - - Rackspace
Block all traffic by default and explicitly enable only specific traffic to known services. This strategy provides good control over the ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@mockdeep a significant downside of “eslint:all” would be that every time we added a new rule, that would automatically be enabled for you. In essence, “eslint:all” would be different every time you upgrade ESLint, meaning you’d constantly need to update your config for every upgrade.
Technically, that would be a breaking change every time we add a rule, and I’m not sure that’s good for anybody.
@platinumazure thanks, I’ll use separate configs, as you suggested on gitter.