-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Video: Use a unique 'key' in the 'TrackList' component #70263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice little improvement :)
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
As they say, the |
Size Change: +1 B (0%) Total Size: 1.85 MB
ℹ️ View Unchanged
|
Co-authored-by: Mamaduka <mamaduka@git.wordpress.org> Co-authored-by: fabiankaegy <fabiankaegy@git.wordpress.org>
What?
PR updates the
TrackList
component to use track source as a unique key instead of the array index. Noticed while reviewing a related PR.This also makes track list rendering more consistent.
gutenberg/packages/block-library/src/video/tracks.js
Line 3 in 68ce198
Why?
See: https://react.dev/learn/rendering-lists#rules-of-keys
Testing Instructions
None. This is a minor improvement in code quality.