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] destructuring-assignment, no-multi-comp, no-unstable-nested-components
, component detection: improve component detection
#3001
[Fix] destructuring-assignment, no-multi-comp, no-unstable-nested-components
, component detection: improve component detection
#3001
Conversation
…d-components`, component detection: improve component detection
Codecov Report
@@ Coverage Diff @@
## master #3001 +/- ##
=======================================
Coverage 97.21% 97.22%
=======================================
Files 110 110
Lines 7297 7305 +8
Branches 2657 2663 +6
=======================================
+ Hits 7094 7102 +8
Misses 203 203
Continue to review full report at Codecov.
|
0d9ef7b
to
860ebea
Compare
no-unstable-nested-components
, component detection: improve component detection
Thanks for your work. |
Not sure if it's caused by the changes in this PR, but after updating from 7.24 to 7.26, I noticed a bunch of false positives showing up in my code:
|
There were some false positives when checking for destructuring: jsx-eslint/eslint-plugin-react#3001 (comment)
@ThiefMaster i agree those are false positives. Can you file a new issue so we can track fixing it? |
There were some false positives when checking for destructuring: jsx-eslint/eslint-plugin-react#3001 (comment)
Fixes: #2956
Description:
Example code that shows incorrect error:
Error shows up because
getParentComponent
callsgetParentStatelessComponent
that callsgetStatelessComponent
on theArrowFunctionExpression
(val =>...) in the example code above which incorrectly returns the sameArrowFunctionExpression
instead ofundefined
.