-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
fix(typescript-estree): fix error handling on ImportExpression
#6587
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(typescript-estree): fix error handling on ImportExpression
#6587
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 site settings. |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## v6 #6587 +/- ##
==========================================
- Coverage 87.49% 87.49% -0.01%
==========================================
Files 365 365
Lines 12511 12512 +1
Branches 3694 3695 +1
==========================================
Hits 10947 10947
- Misses 1202 1203 +1
Partials 362 362
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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.
ImportExpression
ImportExpression
PR Checklist
Overview
When parsing
import()
, there is nonode.arguments[0].getStart
to call.CI log