Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(linter/typescript): support consistent-type-imports rule #2022

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Dunqing
Copy link
Member

@Dunqing Dunqing commented Jan 13, 2024

No description provided.

@Dunqing
Copy link
Member Author

Dunqing commented Jan 13, 2024

@github-actions github-actions bot added the A-linter Area - Linter label Jan 13, 2024
Copy link

codspeed-hq bot commented Jan 13, 2024

CodSpeed Performance Report

Merging #2022 will degrade performances by 3.19%

Comparing 01-13-feat_linter/typescript_support_consistent-type-imports_rule (011e290) with main (919a506)

Summary

❌ 1 regressions
✅ 33 untouched benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

Benchmark main 01-13-feat_linter/typescript_support_consistent-type-imports_rule Change
parser_napi[checker.ts] 231.3 ms 238.9 ms -3.19%

@Dunqing
Copy link
Member Author

Dunqing commented Jan 13, 2024

Blocked by #2023

Base automatically changed from 01-13-feat_ast_visit_TSTypeQuery to main January 13, 2024 16:38
@Dunqing Dunqing force-pushed the 01-13-feat_linter/typescript_support_consistent-type-imports_rule branch from 7933eb0 to 2a15f4a Compare January 31, 2024 05:35
@Dunqing Dunqing force-pushed the 01-13-feat_linter/typescript_support_consistent-type-imports_rule branch from 2a15f4a to 011e290 Compare March 22, 2024 03:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-linter Area - Linter
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant