BREAKING: Update @typescript-eslint parser and plugin
#230
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The packages `@typescript-eslint/parser` and `@typescript-eslint/plugin` have been updated from v4 to v5. We are affected only by the changes to the recommended configuration. The rule `@typescript-eslint/explicit-module-boundary-types` is no longer recommended, so we don't have to explicitly disable it anymore. There are two new recommended rules: `@typescript-eslint/no-loss-of-precision` [1] and `@typescript-eslint/no-unnecessary-type-constraint` [2]. Both of these new rules seem useful, so they have been left enabled. [1]: https://typescript-eslint.io/rules/no-loss-of-precision [2]: https://typescript-eslint.io/rules/no-unnecessary-type-constraint
Gudahtt
force-pushed
the
update-typescript-eslint-parser-and-plugin
branch
from
c086d8d to
78e2319
Compare
Gudahtt
changed the title
@typescript-eslint parser and plugin@typescript-eslint parser and plugin
brad-decker
approved these changes
Aug 15, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
BREAKING: The packages
@typescript-eslint/parserand@typescript-eslint/pluginhave been updated from v4 to v5.We are affected only by the changes to the recommended configuration. The rule
@typescript-eslint/explicit-module-boundary-typesis no longer recommended, so we don't have to explicitly disable it anymore. There are two new recommended rules:@typescript-eslint/no-loss-of-precisionand@typescript-eslint/no-unnecessary-type-constraint.Both of these new rules seem useful, so they have been left enabled.