feat(linter/typescript): support consistent-type-imports rule#2022
Closed
feat(linter/typescript): support consistent-type-imports rule#2022
Conversation
Member
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
CodSpeed Performance ReportMerging #2022 will degrade performances by 3.19%Comparing Summary
Benchmarks breakdown
|
Member
Author
|
Blocked by #2023 |
Dunqing
force-pushed
the
01-13-feat_linter/typescript_support_consistent-type-imports_rule
branch
from
7933eb0 to
2a15f4a
Compare
Dunqing
force-pushed
the
01-13-feat_linter/typescript_support_consistent-type-imports_rule
branch
from
2a15f4a to
011e290
Compare
Member
|
See PR #3895 |
Boshen
deleted the
01-13-feat_linter/typescript_support_consistent-type-imports_rule
branch
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
No description provided.