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