Important note about `set` functions missing from new `useState` docs
還沒有人認領這個 Issue。
- 主要語言
- JavaScript
- 星號
- 11.8k
- 分支
- 7.9k
- 平均合併
- 1 天 11 小時
- 30 天內合併 PR
- 11
描述
I was attending a class about useCallback in conjunction with useState in a custom hook, and the solution to my exercise used an empty dependency array in useCallback, even though it used a setValue from a state:
const [value, setValue] = React.useState(initialValue);
const toggleValue = React.useCallback(
() => setValue((currentValue) => !currentValue),
[] # I put [setValue] here
);
return [value, toggleValue];
I wasn't sure if this was ok, but didn't find any info about this in the new docs of useState. I asked around and found that the old docs do contain the specific information I was looking for:

I'd like to suggest to add this note or something similar in the new docs as well. It might have been omitted for a good reason, but it does feel like important information to me.
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
從新的 useState 文件開始,具體查看 issue 中連結的 setstate 部分,並將其與對應的 Legacy Hooks 參考文件進行比較。新增缺少的註記,或補上關於 set 函式與 useCallback 相依性的等效說明,然後確認呈現後的文件中的指引清楚易懂。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- javascript, react
- 領域
- documentation
- Issue 類型
- 文件
- 難度
- 1/5
- 預估耗時
- 1 小時以內
- 活躍度
- 停滯
- 描述清晰度
- 描述清楚
- 新手友好度
- 45/100