Reactjs.org: Add componentDidCatch to React.Component page

[bvaughn]

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.

[cyan33]

Can I try this? I really love this newly brought feature in React16! :)

[bvaughn]

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!

[cyan33]

@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.

For more details, check [*Error Handling in React 16*](../blog/2017/07/26/error-handling-in-react-16.html).

[bvaughn]

You should be able to link to /blog/2017/07/26/error-handling-in-react-16.html (no leading "../")

[cyan33]

Thanks Brian. :smile:

[bvaughn]

Closed via #136
Thanks!

[merlinpatt]

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 componentStack. Are there more keys?

[bvaughn]

componentStack is the only current key.

This is mentioned here:
https://reactjs.org/docs/error-boundaries.html#componentdidcatch-parameters

But yea, we should either cross-link or expand in the Component API page too.

[merlinpatt]

What future keys do you plan to add to info?

[bvaughn]

No plans / unknown