-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
feat(typescript-estree): gate all errors behind allowInvalidAST #11693
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
base: main
Are you sure you want to change the base?
Conversation
|
Thanks for the PR, @fisker! 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. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
View your CI Pipeline Execution ↗ for commit 9e06baf
☁️ Nx Cloud last updated this comment at |
Codecov Report❌ Patch coverage is
❌ Your patch check has failed because the patch coverage (29.62%) is below the target coverage (90.00%). You can increase the patch coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## main #11693 +/- ##
==========================================
+ Coverage 90.67% 90.68% +0.01%
==========================================
Files 518 518
Lines 52466 52458 -8
Branches 8694 8695 +1
==========================================
- Hits 47571 47569 -2
+ Misses 4881 4874 -7
- Partials 14 15 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
Converter#throwUnlessAllowInvalidAST()There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I understand this, it's actually a pretty big change for the conversion logic, right? If so - that makes sense to me, and I think it's actually quite nice to put all the syntax errors behind the "should the converter throw on invalid syntax?" option. But someone else from @typescript-eslint/triage-team should probably gut check this too.

PR Checklist
Overview
Currently, these errors are all syntax errors, and having two methods is confusing. Let's put all these errors behind
allowInvalidASToption.