We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When declaring a class like this:
class StoreListItem extends React.PureComponent { // A bunch of stuff here }
And then add wrapping it in React.forwardRef like this:
React.forwardRef
export default React.forwardRef((props, ref) => <StoreListItem {...props} forwardRef={ref} />);
The ESLint react/no-multi-comp rule gets triggered. Shouldn't this code be allowed?
react/no-multi-comp
The text was updated successfully, but these errors were encountered:
indeed it should; same with memo or lazy.
Sorry, something went wrong.
@ljharb Anyone working on it? I would like to take a look at it.
Nope, go for it.
Successfully merging a pull request may close this issue.
When declaring a class like this:
And then add wrapping it in
React.forwardRef
like this:The ESLint
react/no-multi-comp
rule gets triggered. Shouldn't this code be allowed?The text was updated successfully, but these errors were encountered: