-
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
Add componentDidCatch to React.Component page #120
Comments
Can I try this? I really love this newly brought feature in React16! :) |
Sure! This issue is all yours! 😄 I've added an "in-progress" label so that others will know not to start work on the issue. If you change your mind about the issue, no worries! Just let me know so that I can remove the label and free it up for someone else to claim. Cheers! |
@bvaughn Hi, thanks for giving me this opportunity. I've added all the necessary document. But right now I'm having a problem on referencing that blog post in the document markdown. Could you please help me with that? This is how I tried but it redirects to the bottom of the new page.
|
You should be able to link to |
Thanks Brian. 😄 |
Closed via #136 |
I would like to see this expanded to include better docs about info. Came here through a trail from facebook/react#10461 - decompose info parameter. I would do it but the only part I am aware of is |
This is mentioned here: But yea, we should either cross-link or expand in the Component API page too. |
What future keys do you plan to add to info? |
No plans / unknown |
Add
componentDidCatch
to https://reactjs.org/docs/react-component.html and link to https://reactjs.org/blog/2017/07/26/error-handling-in-react-16.html for a more complete explanation.The text was updated successfully, but these errors were encountered: