You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whenever tracks are loaded into the player, we reverse the ordering.
This makes sense for Radio4000 channels as we want the newest track (e.g. last) rendered first in the list. But it does not make sense when you load something that isn't a Radio4000 channel, like local files. There you expect it to have whichever order you pass in.
Whenever tracks are loaded into the player, we reverse the ordering.
This makes sense for Radio4000 channels as we want the newest track (e.g. last) rendered first in the list. But it does not make sense when you load something that isn't a Radio4000 channel, like local files. There you expect it to have whichever order you pass in.
The reverse is here: https://github.com/internet4000/radio4000-player/blob/master/src/Radio4000Player.vue#L171
And we also sort tracks fetched from R4 API here: https://github.com/internet4000/radio4000-player/blob/master/src/utils/store.js#L44
Not sure we do both but if we can ensure the reversing is only done for R4 channels and not when set through
updatePlaylist()
we should be good.The text was updated successfully, but these errors were encountered: