Forgotten request for componentDidCatch
還沒有人認領這個 Issue。
- 主要語言
- JavaScript
- 星號
- 11.8k
- 分支
- 7.9k
- 平均合併
- 1 天 11 小時
- 30 天內合併 PR
- 11
描述
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
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
先檢視相關的 issue 10461、10922,以及 reactjs.org issue 17,以還原原始請求及其討論內容。該 issue 未指定檔案、測試、實作入口或完成條件;需要先定義所需的 error-info 物件和適當的 repository。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- javascript, react
- 領域
- documentation, frontend
- Issue 類型
- 功能
- 難度
- 5/5
- 預估耗時
- 一週以上
- 活躍度
- 停滯
- 描述清晰度
- 需要釐清
- 新手友好度
- 20/100