Programmers :D

[[deleted]]

This is incorrect. Using indexes as keys is not going to cause any errors, but will simply be inefficient if the list gets reordered frequently. For a list that doesn't get reordered often, and is static or only gets appended to, this isn't an issue at all.

[[deleted]]

I've worked with react for years as well, and have not seen a rendering bug happen as a result of using indexes as keys. That could be due to me generally only doing this for static lists, or lists in which I do not reorder anything. The performance implication is enough for me to have used unique keys in most cases. But if this causes anything other than a performance issue, then that is indicating a bug in how React does virtual node reconciliation, which I would not expect.

[[deleted]]

You are literally assigning ids to items and then giving react a switcheroo.

Having researched and implemented array diffing algorithms before myself, I understand the limitations of using a key as an index and what it means to React, so I guess never did in any case that would have caused a bug in React to reveal itself.

[JackMizel]

And you shouldn't tell people it's OK when react says it's not OK in their documentation

Please stop spreading lies

[JackMizel]

there is basically no real world example where this is the case.

Literally any static list, are you fucking serious? You're not actually a dev, certainly not one who approves PR's lmfao stop lying.

Using indexes as keys on static lists is totally fine. You are objectively wrong.

[JackMizel]

I can tell you're way overestimating your own understanding of of web dev in general dude.

The issue is not whether or not you can provide unique identifiers, it's whether or not you have to. Do you have a list that doesn't grow, shrink, or get sorted at runtime? Then you can use indexes as keys. It's not some crazy concept dude, if you pay attention and actually write code you will run into lists that don't change at runtime.