Releases: xojs/eslint-config-xo-typescript
Releases · xojs/eslint-config-xo-typescript
v2.0.0
Breaking
New rules
@typescript-eslint/prefer-find
0b25758@typescript-eslint/no-array-delete
819862d@typescript-eslint/prefer-promise-reject-errors
9533972
Improvements
@typescript-eslint/switch-exhaustiveness-check
: Make it stricter df07e88
v1.0.1
- Disable the
import/named
rule f1bdb3b
v1.0.0
Breaking
- Require Node.js 16 and @typescript-eslint/eslint-plugin 6 5f7c768
New rules
Improvements
- Disable the
@typescript-eslint/no-redundant-type-constituents
rule 59a5d77 - Don’t disable the
unicorn/no-null
rule 6b735fd
Fixes
v0.57.0
v0.56.0
- Restore
@typescript-eslint/no-unsafe-argument
rule (#70) 4fd54c2
v0.55.1
v0.55.0
- Add
@typescript-eslint/no-unsafe-declaration-merging
rule 3ec1f94 @typescript-eslint/consistent-type-imports
: Add option to prefer inline type imports e41f4a4
v0.54.1
- Mistake. Please ignore.
v0.53.0
New rules
@typescript-eslint/consistent-type-exports
829d012@typescript-eslint/consistent-type-imports
a1bdfc9
Improvements
- Add options to
@typescript-eslint/prefer-nullish-coalescing
rule f4cf50d
v0.52.0
New rules
@typescript-eslint/consistent-generic-constructors
e15cd30@typescript-eslint/consistent-type-definitions
7decafctype
andinterface
are almost interchangeable. The main difference is thatinterface
can be extended from anywhere, which can be useful in a few cases, but can most often cause surprising hard to track down behavior. XO prefers being strict by default and have chosentype
. Just use aneslint-disable
comment in the few cases where you need the declaration to be extendable.- More info