docs: Update one of You Might Not Need an Effect examples
#8216
Conversation
Using setState inherently causes another re-render on change, even if according to the value nothing changed. useRef would be more accurate
|
Hi @ofek-frame! 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 cla@meta.com. Thanks! |
Size changesDetails📦 Next.js Bundle Analysis for react-devThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
ofek-frame
changed the title
You Might Not Need an Effect exam,plesYou Might Not Need an Effect examples
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
1 participant
Using setState inherently causes another re-render on change, even if according to the value nothing changed.
I think
useRefwould be more accurate.I see the lint error on the changed example - but it might be overzealous, as we indeed don't want to re-render on its change.