-
-
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(utils): add parser name to thrown parser error message #8484
Conversation
Thanks for the PR, @disaacson! 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. |
Apologies. Let me squash the commits. |
@disaacson no need to rebase or squash 🙂. We prefer the raw, unedited history. https://typescript-eslint.io/contributing/pull-requests |
Using the example in the automated test for that error, it would now output
The information that the parser it found was |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #8484 +/- ##
==========================================
- Coverage 87.23% 87.13% -0.10%
==========================================
Files 251 251
Lines 12319 12270 -49
Branches 3884 3868 -16
==========================================
- Hits 10746 10691 -55
- Misses 1303 1307 +4
- Partials 270 272 +2
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.
LGTM, thanks! 🙌
Will wait for @bradzacher a bit as Brad was also commenting on the issue.
…ts to root of the file
I looked into the failed check for I'll leave it alone for now, but let me know if you'd like me to trigger it with an empty commit. Error in check:
|
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.
Is there anything else you'd like me to change @bradzacher or @JoshuaKGoldberg? |
@disaacson, As per our contributing guidelines this PR is in the queue of PRs to reviewed, and will be reviewed when we are able. This project is run by volunteer maintainers, so it might be a bit before we can find the time to get to it. |
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.
PR Checklist
Overview
An error is thrown if there is an issue with the detected parser. This change adds information on the parser that is causing the error to be thrown.
Current message:
This change adds the following detail to the error message:
Parser: <detected parser causing the error>