-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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(typescript-estree): allow erroring on TypeScript syntactic diagn… #6271
feat(typescript-estree): allow erroring on TypeScript syntactic diagn… #6271
Conversation
…ostics, not semantic
Thanks for the PR, @JoshuaKGoldberg! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. |
PR Checklist
Overview
Adds a
TypeScriptIssueDetection
enum so typescript-estree can be told to callprogram.getSyntacticDiagnostics(ast)
but notprogram.getSemanticDiagnostics(ast)
.Note that this is partially in conflict with #6066. That PR removes the partial program; this PR explicitly uses it.
It would be nice to have performance testing in place (#6218). I removed all type checking from
.eslintrc.js
(recommended-requiring-type-checking
,deprecation/deprecation
, and a few assorted rules, deleted inline commends referring to type-checked rules, and ranhyperfine "npx eslint ."
:So, a 4% slowdown penalty for asking for syntactic diagnostics? That might just be worth it.
Either way, filed microsoft/TypeScript#52011 about some syntactic issues being reported as semantic diagnostics.
Competitor/sibling to #6247.