-
-
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
Support detecting React.forwardRef/React.memo #2089
Support detecting React.forwardRef/React.memo #2089
Conversation
This updates the component detection to allow for considering components wrapped in either React.forwardRef or React.memo.
efb7ee5
to
341bb4f
Compare
if (node.type !== 'CallExpression') { | ||
return false; | ||
} | ||
const propertyNames = ['forwardRef', 'memo']; |
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.
Should these kick in only when the React version setting is 16.3 and 16.6 respectively?
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.
Should they? Would this break anything for people on earlier versions?
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.
Probably not, no - but it might be weird to see a warning about a React feature that you can’t use yet.
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.
This wouldn't show any warnings related to the features. It only improves the detection of components using them. So, if they aren't use the features, nothing happens, right? But I could see the case for not running the check on earlier versions.
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.
Yeah that’s a fair point too. I’m not really sure whether it’s better to keep it simple and run the checks always, or to only run the checks when the version dictates.
4704762
to
2010245
Compare
Also, the detection actually works now.
2010245
to
3ce2078
Compare
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 for the clean up on the lib utils.
This updates the component detection to allow for considering components
wrapped in either React.forwardRef or React.memo.
Resolves #1841. Resolves #2059