-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
feat(typescript-eslint): improve undefined extension handling #10177
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-eslint): improve undefined extension handling #10177
Conversation
Thanks for the PR, @mstykow! 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 site configuration. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #10177 +/- ##
=======================================
Coverage 86.18% 86.19%
=======================================
Files 430 430
Lines 15055 15064 +9
Branches 4368 4371 +3
=======================================
+ Hits 12975 12984 +9
Misses 1728 1728
Partials 352 352
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Addresses typescript-eslint#10176 by checking if any of the extensions are undefined and throwing a helpful error if true. Signed-off-by: Maxim Stykow <maxim.stykow@gmail.com>
015b762
to
80f6ba5
Compare
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.
A good start! 🚀
Signed-off-by: Maxim Stykow <maxim.stykow@gmail.com>
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.
🚀
Signed-off-by: Maxim Stykow <maxim.stykow@gmail.com>
@JoshuaKGoldberg sorry to bug you for another review but i didn't know how to retrigger the pipeline without another commit (it was failing at a step that looked unrelated to my changes). |
@JoshuaKGoldberg friendly ping :) |
Looks like you found the right way 🙂! Any PR that's not labeled |
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.
LGTM! Just one suggestion that we can auto-apply before merge IMO.
Signed-off-by: Maxim Stykow <maxim.stykow@gmail.com>
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.
Looks good, thanks!
ad9d3ba
into
typescript-eslint:main
PR Checklist
Overview
Addresses #10176 by checking if any of the extensions are undefined and throwing a helpful error if true.
An alternative would be to filter out undefined extensions and again swallow the errors silently. But I think it's overall an improvement to actually raise an error because an undefined an extension is likely not what the user intended.