-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Closed
Labels
enhancementNew feature or requestNew feature or requestpackage: eslint-pluginIssues related to @typescript-eslint/eslint-pluginIssues related to @typescript-eslint/eslint-pluginrecommended-rulesDiscussion about recommended rule setsDiscussion about recommended rule sets
Description
While looking at #591, I encountered something that I wanted to discuss separately.
Intuitively, I would think that a typical config could look like this:
{
extends: [
// start from this
'eslint:recommended',
// disable rules that are incompatible with TS or better handled by it
'@typescript-eslint/eslint-recommended',
// turn on TS-specific recommended rules
'@typescript-eslint/recommended'
]
However, @typescript-eslint/eslint-recommended
already contains some opinionated rules so adding it to our config actually yielded some new errors, which I wouldn't have expected.
I think I'd prefer if eslint-recommended
was just a compatibility config while all the additional, opinionated and possibly stricter rules were in recommended
. What do you think?
teppeis, CvX and glen-84
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestpackage: eslint-pluginIssues related to @typescript-eslint/eslint-pluginIssues related to @typescript-eslint/eslint-pluginrecommended-rulesDiscussion about recommended rule setsDiscussion about recommended rule sets