Fixed playlist tracks retrieval through the web API. #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The format returned by /user/<user_id>/playlists/<playlist_id> is
actually something like { ... "tracks": {"items": [{...}] } ... }.
The "summarized" playlist output returned by /me/playlists instead
describes the tracks through their href:
{ ... "tracks": {"total"123, "href": "https://api.spotify.com/v1/users/me/playlists/<id>/tracks" ... } }
a playlist by URI would fail as web_client is not previously declared
…e playlist when downloading it, otherwise Spotify will return only the (100) results on the first page
… type - Implemented proper playlists versioning and cache invalidation using the Spotify snapshot_id - Improved performance - before the lookup method with the playlist expansion was called more than once, now it only happens at startup - Removed unneeded web_client code in the translator module
…ylist expansion that left playlists with 100 items max)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The format returned by
/user/<user_id>/playlists/<playlist_id>isactually something like
{ ... "tracks": {"items": [{...}] } ... }.The "summarized" playlist output returned by
/me/playlistsinsteaddescribes the tracks through their href:
{ ... "tracks": {"total"123, "href": "https://api.spotify.com/v1/users/me/playlists/<id>/tracks" ... } }