Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Tracks have persistent IDs #2
This is important for implementations where the favorite-d status is being stored in
In that situation, when a track is moved to the top of the playlist, the index-based keys code would cause React to believe that the track which is now in the position of the track that was moved to the top of the list, is the one which still has the favorite status.
(Basically, if you don't do this then "favorite" status is more associated with a particular index in the track list, rather than a particular track.)