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
I wanted somewhere to keep track of the breaking changes we should make as part of a 2.0.0 release.
Deprecated Rules:
- (prfeat(eslint-plugin)!: remove deprecated rules #739) remove deprecated rule
prefer-interface
(replaced byconsistent-type-definitions
) - (prfeat(eslint-plugin)!: remove deprecated rules #739) remove deprecated rule
no-triple-slash-reference
(replaced bytriple-slash-reference
) - (prfeat(eslint-plugin)!: add rule
consistent-type-assertions
#731) remove deprecated ruleno-angle-bracket-type-assertion
(replaced byconsistent-type-assertions
) - (prfeat(eslint-plugin)!: add rule
consistent-type-assertions
#731) remove deprecated ruleno-object-literal-type-assertion
(replaced byconsistent-type-assertions
)
Misc:
- (prfeat: Support eslint@6 #645) Support eslint 6 (drop node 6 support)
- (prfix(eslint-plugin)!: remove "isTypescriptFile". #594) kill
isTypescriptFile
checksMake typescript-eslint rules compatible with .vue files #524 - (prfeat(eslint-plugin)!: add rule
consistent-type-assertions
#731) generalizeno-angle-bracket-type-assertion
(Rule suggestion: generalize @typescript-eslint/no-angle-bracket-type-assertion #332) and merge inno-object-literal-type-assertion
- (prfeat(typescript-estree)!: throw error on file not in project when
project
set #760) protection against most common performance pitfall - (prfix(eslint-plugin): [explicit-function-return-type] Fix allowExpressions ignoring default exports #831)
explicit-function-return-type
allowExpressions
shouldn't ignoreexport default () => {}
renamewill do in v3@typescript-eslint/experimental-utils
to@typescript-eslint/utils
(feat: Move shared types into their own package #425 (review))look into renaming a number of rulesSuggestion: standardize against prefixing rule names with "no-" #203will do with a later major bump..
Recommended stuff:
- reevaluate rule defaults
- (prfeat(eslint-plugin)!: change recommended config #729) make
explicit-function-return-type
more relaxed by default, as it's the standard usage ([explicit-function-return-type] Consider allowExpressions=true and allowTypedFunctionExpressions=true as default #493) - (feat(eslint-plugin)!: [promise-function-async] make allowAny default true #733) Remove the
allowAny
option from thepromise-function-async
rule and make it the default (from comment below)
- (prfeat(eslint-plugin)!: change recommended config #729) make
- (prfeat(eslint-plugin)!: change recommended config #729) update the recommended rule set with new rules (and remove some rules)[recommended] Remove stylistic rules from recommended #651
- (prfeat(eslint-plugin)!: recommended-requiring-type-checking config #846) split the recommended into a base set not requiring type info, and an extension set requiring type info, so people can have a fast experience by default.