Don't quite see using index as key has problems?
还没有人认领这个 Issue。
- 主要语言
- JavaScript
- 星标
- 11.8k
- 派生
- 7.9k
- 平均合并
- 1 天 11 小时
- 30 天内合并 PR
- 11
描述
On page https://reactjs.org/docs/reconciliation.html
it is said that
Here is an example of the issues that can be caused by using indexes as keys on CodePen
How can the issue be created? I added record to the front, to the back, and sort them, and they seemed to work ok?
Actually, here is a simple case and I can't break it: https://stackoverflow.com/questions/60283967/in-reactjs-using-array-index-as-key-is-said-to-not-work-well-but-i-cant-make
I can only break it if it is all 3 conditions:
It has to be function component using useState, and I have to mutate the state (which the docs says I shouldn't do), and use index as key. So if I don't mutate the state, I can't make it not work well if I use index as key.
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
先从 reconciliation 文档页面及其中链接的 CodePen 示例开始,然后将报告的行为与链接的 Stack Overflow 案例进行比较。确定示例或说明是否需要澄清,并在文档准确解释了一个可复现的案例,或准确解释了当前示例为何仍然有效时,视文档为完整。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- javascript, react
- 领域
- documentation
- Issue 类型
- 文档
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 35/100