feat(configs): add new severity option for all rules (#733) #736
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #736 +/- ##
=======================================
Coverage 75.54% 75.54%
=======================================
Files 122 122
Lines 24456 24456
Branches 4670 4670
=======================================
Hits 18476 18476
Misses 5980 5980 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Personally I think this warranted a major version update. One of the reasons my configs are big, is because I override most rules to warn, or use the eslint only-warn plugin. But this is a neat change that will help out a lot of people. Perhaps its something that could be mentioned in the release notes for the next version in case it flew under the radar for some folks. Als already mentioned previously, I feel that stylistic problems should always be warnings and perhaps it can be the default, but overall its nice that we can now configure it globally. Nicely done on this new feature! |
Description
This PR introduces a new severity option that allows users to configure all rules as warnings instead of errors. This helps developers reduce distractions in their IDEs while still enforcing strict rule compliance at commit time.
Linked Issues
Closes #733
Additional context
Would it be helpful to provide predefined
recommended-warnandall-warnpresets with warning severity? This would allow users to enable a warning-based configuration more easily without needing to use customize method.