Use good keys when rendering arrays of components #675
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In this PR I make sure that all rows and group of rows have unique keys that don't change. Previously we were using the index. This should make React's reconciliation algorithm faster when doing operations such as filtering. See https://legacy.reactjs.org/docs/reconciliation.html for more information about this algorithm.
I profiled locally when filtering out and in a platform, and this seems a bit faster than previously.
I'm requesting review from Beatrice because she should know whether my assumptions are correct.