Update ESLint config, migrate some rules away from TSLint #5272
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes proposed in this pull request:
sort-imports
rule, apply auto fixer to re-sort import statements@typescript-eslint/no-extraneous-class
rulevariable-name
-> ESLint@typescript-eslint/naming-convention
ruleonly-arrow-functions
rule (already covered by ESLintprefer-arrow-callback
)This leaves just
no-submodule-imports
andobject-literal-sort-keys
enabled in the TSLint config. There are no equivalent lint rules out there that do exactly what we want here, so we'll have to implement some new rules ourselves if we want to fully migrate away from TSLint.See typescript-eslint/ROADMAP.