Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork2.8k
feat(typescript-estree): private identifiers can only appear on LHS of in expressions#9232
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
feat(typescript-estree): private identifiers can only appear on LHS of in expressions#9232
Conversation
Thanks for the PR,@Josh-Cena! 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 onhttps://opencollective.com/typescript-eslint. |
netlifybot commentedJun 3, 2024 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
✅ Deploy Preview fortypescript-eslint ready!
To edit notification comments on pull requests, go to yourNetlify project configuration. |
nx-cloudbot commentedJun 3, 2024 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
View yourCI Pipeline Execution ↗ for commit546a854
☁️Nx Cloud last updated this comment at |
Converting it to draft, because TS is very wack about private identifiers: |
👋 just checking in@Josh-Cena, is there anything we should do with this? |
Chatted 1:1, this is blocked on a resolution tomicrosoft/TypeScript#58754. |
Since the TS fix has been languishing with no progress for over a year, can we just move forward with this on our side? Or do we need to keep this hard-blocked? |
Yeah, I think we should consider ourselves un-blocked at this point. |
Uh oh!
There was an error while loading.Please reload this page.
codecovbot commentedSep 29, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Codecov Report❌ Patch coverage is
❌ Your patch status has failed because the patch coverage (23.07%) is below the target coverage (90.00%). You can increase the patch coverage or adjust thetarget coverage. Additional details and impacted files@@ Coverage Diff @@## main #9232 +/- ##==========================================- Coverage 90.93% 90.72% -0.21%========================================== Files 506 516 +10 Lines 51394 52027 +633 Branches 8482 8596 +114 ==========================================+ Hits 46735 47203 +468- Misses 4646 4810 +164- Partials 13 14 +1
Flags with carried forward coverage won't be shown.Click here to find out more.
🚀 New features to boost your workflow:
|
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! I think I'm mildly in favor of@kirkwaiblinger's suggestion, so I'll defer to you two on that. 🙂
Co-authored-by: Kirk Waiblinger <53019676+kirkwaiblinger@users.noreply.github.com>
d29bd0a
intotypescript-eslint:mainUh oh!
There was an error while loading.Please reload this page.
PR Checklist
PrivateIdentifier
can only be LHS ofBinaryExpression[operator='in']
#9222Overview