[Typo]: The mechanism described in "Providing a fallback for server errors and client-only content" behaves differently in practice
還沒有人認領這個 Issue。
評估
- 難度
- 2/5
- 預估耗時
- 1-3 小時
- 新手友好度
- 68/100
- Issue 類型
- 文件
- 描述清晰度
- 基本清楚
- 活躍度
- 冷清
- 技術堆疊
- javascript, react
研究方向
從 React Suspense 參考文件中的「Providing a fallback for server errors and client-only content」一節開始，尤其關注關於伺服器錯誤和選擇退出伺服器端渲染的兩則引述。重現或驗證回報的開發環境和生產環境行為，包括錯誤 419，然後更新該節，使其說明與觀察到的行為一致，並清楚說明任何限制或受支援的方法。
由索引模型根據 Issue 內容生成。
描述
Summary
The section "Providing a fallback for server errors and client-only content" could be misleading when it comes to opting out of server-rendering.
Page
Details
The section "Providing a fallback for server errors and client-only content" seems to suggest that if a user wants to explicitly opt out a component/hook out of being rendered on the server, they can throw an error on the server, and when that same component successfully renders on the client, the error will not be surfaced to the user. I am specifically talking about the following statements:
However, if it does not error on the client, React will not display the error to the user since the content was eventually displayed successfully.
You can use this to opt out some components from rendering on the server. To do this, throw an error in the server environment and then wrap them in a boundary to replace their HTML with fallbacks:
That seems to be in opposition to how React behaves in practice. Both in development and in production, the error thrown on the server is surfaced to the developer, and (arguably) the end user through the browser console (Minified error description: https://react.dev/errors/419).
The seems to be no documented way to distinguish an intended opt-out from a user error, and if there is none, I feel like the documentation is a bit misleading.
- 主要語言
- JavaScript
- 星號
- 11.8k
- 分支
- 7.9k
- 平均合併
- 16 小時 6 分鐘
- 30 天內合併 PR
- 7
貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
reactjs/react.dev 的其他 Issue
-
type: documentation
難度 2/5 1-3 小時 新手友好度 72/100
-
難度 1/5 1 小時以內 新手友好度 82/100
-
bug: unconfirmed
難度 2/5 1-3 小時 新手友好度 74/100
-
type: typos
難度 1/5 1 小時以內 新手友好度 90/100
-
bug: unconfirmed
難度 2/5 1-3 小時 新手友好度 68/100
查看 reactjs/react.dev 的全部 Issue
相似的 Issue
-
bug
難度 2/5 1-3 小時 新手友好度 76/100
avniproject/avni-client#2135 ·
-
enhancement
難度 2/5 1-3 小時 新手友好度 70/100
babalae/bettergi-scripts-list#3674 ·
-
A-Release-Notes C-Editing D-Modest S-Ready-For-Implementation
難度 2/5 1-3 小時 新手友好度 72/100
bevyengine/bevy-website#2595 ·
-
ecosystem wording
難度 1/5 1 小時以內 新手友好度 90/100
matrix-org/matrix.org#3649 ·
-
難度 2/5 1-3 小時 新手友好度 88/100
vadimdemedes/ink#1029 ·