-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
fix(eslint-plugin): [prefer-optional-chain] handle MemberExpression in final chain position #11835
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(eslint-plugin): [prefer-optional-chain] handle MemberExpression in final chain position #11835
Conversation
|
Thanks for the PR, @mdm317! 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 project configuration. |
|
View your CI Pipeline Execution ↗ for commit 2838efc
☁️ Nx Cloud last updated this comment at |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #11835 +/- ##
==========================================
+ Coverage 90.53% 90.55% +0.01%
==========================================
Files 523 523
Lines 53096 53140 +44
Branches 8838 8846 +8
==========================================
+ Hits 48073 48122 +49
+ Misses 5010 5005 -5
Partials 13 13
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|

PR Checklist
[x] That issue was marked as accepting prs
Problem
BinaryExpression nodes where both left and right are MemberExpression are not checked,
a === null || a.b !== foo.three; // bug: should be flagged/fixable, is notand CallExpression nodes whose callee is a MemberExpression are not treated as MemberExpression.
a === null || a.b !== a.c();Fix
MemberBasedExpression, which covers botha.banda.b().unknownto theyodaenumLogic for
yoda: unknownBinaryExpressionnodes where both sides areMemberBasedExpression, setyodatounknown.a.b != a.c,a.b != c.dyodaisunknownand both sides are subsets of theprevious chain, skip the transformation inanalyzeChain.