Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork2.8k
Closed
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 ifeslint-recommended
was just a compatibility config while all the additional, opinionated and possibly stricter rules were inrecommended
. What do you think?