-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
Clarify the definition of "inside conditions" #3542
Conversation
Hi @tywmick! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at [email protected]. Thanks! |
Deploy preview for reactjs ready! Built without sensitive environment variables with commit 7788b81 |
Co-authored-by: Ricky <[email protected]>
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
Thanks! |
I just got tripped up violating the first rule of Hooks in a situation like this:
I'd only been thinking in visual terms about whether
useState
was being called at the top level. Sure, it wasn't inside a conditional statement, but coming after that early exit meant it was still only called under certain conditions, which, now I know, still counts.eslint-plugin-react-hooks does catch this situation, for the record, but the situation confused me so much I thought it might be nice to add a clarification to this page that "don't call Hooks inside conditions" doesn't just mean "inside conditional statements".
useState
here doesn't feel like it's "inside" anything.Might be a better way and/or place to explain this idea, but this is a start, at least.