feat(eslint-plugin): split required typechecking configs #5002
+606
−282
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
We provide all rules in the predefined configs, including the ones that requires type checking. Type checking is automatically enabled, and the configs uses the
tsconfig.jsonfile as project.Closes #4993
Closes #4903
What is the new behavior?
Rules that require typechecking are excluded by default, and can be enabled by using the
abcTypeCheckedconfig. When the user opts into this behavior, the user is also required to configure the correct parsing options.This is similar to https://typescript-eslint.io/getting-started/typed-linting/
Does this PR introduce a breaking change?
Other information
The current set up can be difficult to configure when using multiple projects and/or multiple tsconfig files. I expect this to become a problem on new projects that make of
tsconfig.json(with references) andtsconfig.app.jsonfiles.