-
Notifications
You must be signed in to change notification settings - Fork 47.7k
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
Document error boundaries #10922
Comments
Hey, |
@krizzu give it a go. i will not have time until later this weekend. mind cc-ing me on the branch? |
Just a quick question about Error Boundaries. |
@bogdansoare Don't know anything about performance issues with stacked EB tho. |
Please refer to our post: https://reactjs.org/blog/2017/07/26/error-handling-in-react-16.html It describes the behavior in detail. We should just adopt it to the doc format. |
Yes please. For now it's worth documenting it contains the |
The documentation and source code for reactjs.org now lives in a different repository: reactjs/reactjs.org. (For more info on why we made this move, see issue #11075.) I've moved this issue to the new repo: reactjs/react.dev#17 and tagged it as "in-progress" and belonging to @krizzu. Let's continue the discussion there! Sorry for the inconvenience. |
Error Stack thrown by this API in production mode is almost of no use. Can someone suggest how to decipher that. I have my sourceMaps. This error is located at: |
phone_model: Urban com.facebook.react.common.JavascriptException: TypeError: TypeError: TypeError: Invalid attempt to destructure non-iterable instance This error is located at: This error is located at: This error is located at:
|
I don't think we have either a top-level doc or a
componentDidCatch
reference yet.cc @chantastic
The text was updated successfully, but these errors were encountered: