tamland
Possible to create paginated for v1 API endpoints, like playlist_and_favorite_playlists?
Thank you for creating already several _paginated methods for v2 endpoints. Is it possible also to create such methods also for v1 endpoints, like: playlist_and_favorite_playlists() (https://github.com/EbbLabs/python-tidal/blob/19ca0917d74ab30a1db3a4f791975fcc113d7403/tidalapi/user.py#L191)
Why I am asking? If I use this method playlist_and_favorite_playlists() it returns all user playlists including the playlists within any user folder. This means, if I have 20 playlists in my root folder and 10 playlists in root/my-folder it returns all 30 playlists.
But if I use playlists_paginated (https://github.com/EbbLabs/python-tidal/blob/19ca0917d74ab30a1db3a4f791975fcc113d7403/tidalapi/user.py#L669) it only returns the playlists in the root folder, in my case only 20.
I would like to use your sped up paginated worker for a method, which simply returns all playlists, regardless if they are in a folder or not, basically the behavior of playlist_and_favorite_playlists() but with your pagination worker.
It should be possible, if we can somehow get the number of items that are available. I have not yet checked if this is possible with the response from the endpoint used in playlist_and_favorite_playlists, but I will look into it.
Or let me ask in general: Is it possible to get a paginated version of all the method from User, similar as already implemented in Favorites?
And would this be also possible for the search and for playlist items? Some playlists contains thousands of items.
And would this be also possible for the search and for playlist items? Some playlists contains thousands of items.
Please add a separate feature request for this 👍