Conversation

andyleejordan

The originally recommended migration method resulted in 3,150 problems, and it moved us to an already out-of-date version of ESLint. So I decided to redo this by moving natively to ESLint's recommended configuration (no TSLint migration, except for comment directives) and then allowed ESLint to reformat the codebase. Resolves #2882.

@ghost ghost added Area-Build & Release Issue-EnhancementA feature request (enhancement).labels May 3, 2021
@andyleejordanandyleejordan changed the title WIP: Replace TSLint with ESLint Replace TSLint with ESLint Oct 18, 2022
@andyleejordanandyleejordan marked this pull request as ready for review October 18, 2022 23:50
@andyleejordanandyleejordan requested a review from a team October 18, 2022 23:50
@andyleejordanandyleejordan requested a review from a team as a code owner October 18, 2022 23:50
@andyleejordan

@SeeminglyScience for what it's worth there is also @typescript-eslint/recommended-requiring-type-checking which would be awesome to have...but currently finds over 600 errors.

Except where we have to ignore them individually.
We selectively fixed and enabled most of its warnings, and then disabled
the ones we cannot (for now) fix (mostly due to use of `any`).
@andyleejordan

Ok I turned that on!

@andyleejordan

Followed this essentially: https://typescript-eslint.io/docs/linting/configs/

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@andyleejordanandyleejordan merged commit 817ae25 into main Oct 19, 2022
@andyleejordanandyleejordan deleted the andschwa/eslint branch October 19, 2022 23:17
Sign up for free to join this conversation on . Already have an account? Sign in to comment
Area-Build & Release Issue-EnhancementA feature request (enhancement).
None yet

Successfully merging this pull request may close these issues.

TSLint is deprecated