reactjs / reactjs/react.dev

[Typo]: `useOptimistic` is missing from Hooks reference page

未關閉 適合新手
#8,570 2 則留言 1 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

type: typos
主要語言
JavaScript
星號
11.8k
分支
7.9k
平均合併
1 天 11 小時
30 天內合併 PR
11

描述

Summary

The useOptimistic hook is listed in the left navigation menu but is missing from the Built-in React Hooks overview page, leaving the page incomplete with only 17 of the 18 hooks documented.

Page

https://react.dev/reference/react/hooks

Details
Description

The left navigation menu under Hooks lists 18 hooks, but the Built-in React Hooks overview page only documents 17 of them. useOptimistic is present in the sidebar but not mentioned anywhere on the overview page.

Steps to reproduce
  1. Open https://react.dev/reference/react/hooks
  2. Count the hooks documented on the page
  3. Compare with the hooks listed in the left navigation menu under Hooks
Expected

useOptimistic should be listed in the State Hooks section of the overview page, alongside useState and useReducer, since it lets you show a different state while an async action is pending.

Actual

useOptimistic is missing from the overview page entirely.

Suggested fix

Add useOptimistic to the State Hooks section in src/content/reference/react/hooks.md:

  • useOptimistic lets you show a different state while an async action is pending.
Screen Capture
Image
Additional Context:

The overview page is often the first place developers look when exploring React's built-in hooks. Having useOptimistic absent from this page means:

  • Developers new to React may not discover it exists at all, since the overview page is designed to be the exhaustive entry point for all built-in hooks.
  • It creates an inconsistency between the sidebar navigation and the page content
  • useOptimistic is particularly relevant in modern React apps that use Server Actions and async transitions — a growing pattern — so its visibility on the overview page is especially valuable for developers adopting these features.

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

研究方向

從 src/content/reference/react/hooks.md 開始,檢查 State Hooks 區段,並將其與 Hooks 導覽和 useOptimistic 參考頁面進行比較。確認概覽列出了全部 18 個 hooks,且新的項目以所述描述連結至 /reference/react/useOptimistic。

由索引模型根據 Issue 內容生成。

評估

技術堆疊
javascript, react
領域
documentation
Issue 類型
文件
難度
1/5
預估耗時
1 小時以內
活躍度
冷清
描述清晰度
描述清楚
新手友好度
82/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。