Solve Confusion about executing timing of useEffect #7679
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Hi @DevinJohw! 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! |
Size changes📦 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! 🙌 |
| @@ -66,7 +66,7 @@ function ChatRoom({ roomId }) { | |||
|
|
|||
| * If your Effect is caused by an interaction (like a click), **React may run your Effect before the browser paints the updated screen**. This ensures that the result of the Effect can be observed by the event system. Usually, this works as expected. However, if you must defer the work until after paint, such as an `alert()`, you can use `setTimeout`. See [reactwg/react-18/128](https://github.com/reactwg/react-18/discussions/128) for more information. | |||
|
|
|||
| * Even if your Effect was caused by an interaction (like a click), **React may allow the browser to repaint the screen before processing the state updates inside your Effect.** Usually, this works as expected. However, if you must block the browser from repainting the screen, you need to replace `useEffect` with [`useLayoutEffect`.](/reference/react/useLayoutEffect) | |||
| * Even if your Effect was caused by an interaction (like a click), **React may allow the browser to repaint the screen before executing the code inside your Effect that responds to state updates.** Usually, this works as expected. However, if you must block the browser from repainting the screen, you need to replace `useEffect` with [`useLayoutEffect`.](/reference/react/useLayoutEffect) | |||
There was a problem hiding this comment.
Explained on the issue, but this isn't correct. The point here is that even if effect fire before paint, any state updates inside the effect are rendered after paint.
Solve Confusion about executing timing of useEffect and Remove some redundant whitespace #7678