You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Spinning out of JoshuaKGoldberg/dot-com#140 and a direct conversation with @lydell: now that most ESLint recommended configs/plugins no longer enable formatting rules, it seems that eslint-config-prettier isn't necessary in most projects. Most projects can safely remove it from their "extends" listings. But I still get a lot of questions from folks who think they still need this package as a shared config.
Would it be reasonable to add a mention somewhere in the README.md about when this package is most useful?
In general: as a docs resource / quick checker for rule enablement
For configs: only when you're using a legacy plugin that enables formatting rules?
The text was updated successfully, but these errors were encountered:
There is @eslint-stylistic adopting those rules, I won't clarify them as legacy, but sure, a section about current situation would still be good to have.
Spinning out of JoshuaKGoldberg/dot-com#140 and a direct conversation with @lydell: now that most ESLint recommended configs/plugins no longer enable formatting rules, it seems that
eslint-config-prettier
isn't necessary in most projects. Most projects can safely remove it from their"extends"
listings. But I still get a lot of questions from folks who think they still need this package as a shared config.Would it be reasonable to add a mention somewhere in the README.md about when this package is most useful?
The text was updated successfully, but these errors were encountered: