This repository has been archived by the owner on Jan 23, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 18
guarantee correct remote ordering with sort/limit #9
Comments
simon-weber
added a commit
that referenced
this issue
Nov 26, 2015
serverside sorting will only work for newly-created playlist because of the idempotent delete/add sync. I remember reordering being a total pita in gmusciapi, so we may want to just delete and add every time?
See long comment of a82dace -- we'll either need reorder support, or always delete/add. |
Actually, delete/add probably won't work given how Google partially updates (it's unlikely that partial updates are handled in order). |
Google's interface supports absolute mass-reordering now, which makes this so much easier to implement. I was afraid I was going to have to send O(n) requests per playlist (which I had a trick for optimizing in gmusicapi but never finished). I'll knock this out for the next release. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently, remote playlists are handled like a set: when we update, we add and delete the minimum amount of tracks to result in the desired tracks. This doesn't respect the desired ordering, but does result in the correct tracks.
The text was updated successfully, but these errors were encountered: