Forgotten request for componentDidCatch
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11.8k
- Forks
- 7.9k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 11
Description
An issue was brought up in https://github.com/facebook/react/issues/10461
which highlighted an opportunity for expansion on componentDidCatch(error, info) - being that info only returns one item prop: componentStack; there were a lot of good ideas to break this down into a detailed object of the error with an array for the stack trace.
This issue was then closed for https://github.com/facebook/react/issues/10922 - which told everyone the issue had moved to a new respository - but the referenced issue missed the very initial reason for the request. We didn't just want documentation, we wanted to look at a fuller featured object for error info.
So it was moved and closed again in https://github.com/reactjs/reactjs.org/issues/17
--- Opening this because the original issue from October has been lost:
https://github.com/facebook/react/issues/10461
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked issues 10461, 10922, and reactjs.org issue 17 to recover the original request and its discussion. The issue does not name files, tests, an implementation entry point, or completion criteria; the desired error-info object and the appropriate repository would need to be defined first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- documentation, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100