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 a functional component includes a named function in its body, the react/display-name rule does not trigger for the wrapping component.
react/display-name
export default function () { function fetchData () {} // <-- causes react/display-name not to trigger return <div/>; }
5.15.3
7.12.4
The text was updated successfully, but these errors were encountered:
Although I'd suggest never creating a function inside an SFC (inside the render path), this definitely sounds like a bug.
Sorry, something went wrong.
When using hooks, you almost exclusively often create functions inside FCs.
display-name
That doesn't mean it's a good idea, it just means hooks might encourage that pattern.
No branches or pull requests
When a functional component includes a named function in its body, the
react/display-name
rule does not trigger for the wrapping component.5.15.3
7.12.4
The text was updated successfully, but these errors were encountered: