Add note on error boundary limitations#8108
Conversation
|
Hi @JayCeeKay1991! 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! 🙌 |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
| - Event handlers [(learn more)](/learn/responding-to-events) | ||
| - Asynchronous code (e.g. `setTimeout` or `requestAnimationFrame` callbacks) |
There was a problem hiding this comment.
Can we caveat that with startTransition from useTransition in those scenarios behaving different? Erroring in a Transition that is bound to the Hook version will trigger Error boundaries.
There was a problem hiding this comment.
Thanks for your feedback, I added the exception.
2 participants
Issue #6991
Adding a note about the limitations of Error Boundaries according to the legacy docs.