Before You File a Proposal Please Confirm You Have Done The Following...

• I have searched for related issues and found none that match my proposal.
• I have read the FAQ and my problem is not listed.

Description

Per eslint/eslint#16512, a preference of at least three ESLint or plugin maintainers (myself included) is to use warnings only as a temporary measure:

Warnings were intended to be used temporarily. My belief is that using warnings long term results in people tuning them out as just console noise, so I don’t believe you are getting much benefit with long-term warnings.

Personally, I would advocate switching from warn to error in your strict config. As mentioned, warnings are easily ignored and thus not that useful other than for temporary/transitional usage. If someone opts-in to using your strict config, then presumably they're interested in actually enforcing stricter/more-opinionated rules with actual violations and not just warnings.

Proposal: let's switch meta.docs.recommended to just specify a recommended config family?

- recommended: 'error' | 'strict' | 'warn' | false;
+ recommended: 'recommended' | 'strict' | false;

Impacted Configurations

• recommended
• recommended-requiring-type-checking
• strict

Additional Info

No response