Error handling code for concurrent mode suspense does not properly handle errors
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11.8k
- Forks
- 7.9k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 11
Description
Documentation URL:
https://reactjs.org/docs/concurrent-mode-suspense.html#handling-errors
CodeSandbox URL:
https://codesandbox.io/s/adoring-goodall-8wbn7
The documentation suggests using error boundary to catch rendering or data fetching errors. However, in development, this triggers the "react-error-overlay" due to unhandled runtime error.
Please click on the CodeSandbox link to see the react-error-overlay.
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
Open the linked documentation section and CodeSandbox reproduction first, then compare the documented error-boundary behavior with the development react-error-overlay result. Done means either the example no longer triggers an unhandled runtime overlay or the documentation clearly explains the observed limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- documentation, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100