-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
fix(typescript-estree): the token value of an escaped identifier differs with espree #11116
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?
fix(typescript-estree): the token value of an escaped identifier differs with espree #11116
Conversation
Thanks for the PR, @dbarabashh! 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. |
View your CI Pipeline Execution ↗ for commit 8e99c65.
☁️ Nx Cloud last updated this comment at |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #11116 +/- ##
=======================================
Coverage 90.83% 90.83%
=======================================
Files 497 497
Lines 50279 50291 +12
Branches 8297 8301 +4
=======================================
+ Hits 45672 45684 +12
Misses 4592 4592
Partials 15 15
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
I’m not sure the current CI/CD error is actually caused by my changes but I cant say for certain. I think I need some help. |
It looks like this same error is happening on main branch f7ea991 - so probably it has nothing to do with this PR. |
PR Checklist
Overview