-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
fix(type-utils): ensure external sources don't match for the FileSpecifier
#6866
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
fix(type-utils): ensure external sources don't match for the FileSpecifier
#6866
Conversation
Thanks for the PR, @RebeccaStevens! 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 settings. |
@marekdedic How's this approach look to you? |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## v6 #6866 +/- ##
==========================================
- Coverage 87.46% 87.45% -0.02%
==========================================
Files 374 374
Lines 12879 12892 +13
Branches 3811 3813 +2
==========================================
+ Hits 11265 11275 +10
- Misses 1229 1231 +2
- Partials 385 386 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Hi, thanks for the alternative proposal! Reading quickly through this, I see this mainly builds on the |
Oh actually, I see Sorry, if this does what I think it does then it's great, but as you see, I'm not that well versed with TS internals :/ |
This approach actually relies more on
|
Hmm, yes, that's what I thought in my second comment, sorry for the confusion. I am still not 100% why the type roots are needed - if Anyway, apart from this, LGTM. |
Could you please add a test for this? |
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.
Test coverage please? I see a missing line 😄
Oh, and just for the original question - IMHO, I prefer this to the alternative PR #6860 |
This was unintentionally auto-closed when we merged the |
👋 Hey @RebeccaStevens! Just checking in, is this still something you have time for? No worries if not - I just don't want to leave it hanging. |
Closing this PR as it's been stale for a while without activity. Feel free to reopen @RebeccaStevens if you have time - but no worries if not! If anybody wants to drive it forward, please do post your own PR - and if you use this as a start, consider adding a co-author at the end of your PR description. Thanks! 😊 |
PR Checklist
typeMatchesSpecifier
FileSpecifier
checks in node modules #6819Overview
This is an alternative to #6860 (closes #6860).