feat(typescript-eslint): upgrade to latest to support type export syntax #406
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
Bumps [ts-jest](https://github.com/kulshekhar/ts-jest) from 25.5.1 to 26.0.0. - [Release notes](https://github.com/kulshekhar/ts-jest/releases) - [Changelog](https://github.com/kulshekhar/ts-jest/blob/master/CHANGELOG.md) - [Commits](kulshekhar/ts-jest@v25.5.1...v26.0.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
export type { Something } requires a newer eslint typescript parser. Without this, eslint will be
unable to parse newer TypeScript.
BREAKING CHANGE: The camelcase rule was deprecated in typescript-eslint. I've tried to replace it
with an equivalent naming-convention rule config. I question if we should have this at all.
kirbysayshi
force-pushed
the
ksh/upgrade-typescript-eslint
branch
from
d9533e9
to
088c22f
Compare
|
Going to retarget for release-8.0 branch. |
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.
export type { Something }requires a newer eslint typescript parser. Without this, eslint will beunable to parse newer TypeScript.
BREAKING CHANGE: The camelcase rule was deprecated in typescript-eslint. I've tried to replace it with an equivalent naming-convention rule config. I question if we should have this rule at all!