[GH-ISSUE #50] Automatically support limit/next searches #30

New issue

Closed

opened 2026-02-27 19:25:41 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 19:25:41 +03:00

Owner

Originally created by @andig on GitHub (Jul 17, 2016).
Original GitHub issue: https://github.com/jwilsson/spotify-web-api-php/issues/50

Current api implementation ignores limit/next return values. Large result sets should be automatically handled by the library.

Originally created by @andig on GitHub (Jul 17, 2016). Original GitHub issue: https://github.com/jwilsson/spotify-web-api-php/issues/50 Current api implementation ignores limit/next return values. Large result sets should be automatically handled by the library.

kerem closed this issue

2026-02-27 19:25:41 +03:00

kerem commented

2026-02-27 19:25:42 +03:00

Author

Owner

@andig commented on GitHub (Jul 17, 2016):

Actually, this may be more of a question: I have not found any way to even retrieve paged results without reimplementing the internal logic. Even calling e.g. getUserPlaylist with options for offset/limit it doesn't work as spotify wants to append a /tracks to the uri.

@andig commented on GitHub (Jul 17, 2016): Actually, this may be more of a question: I have not found any way to even retrieve paged results without reimplementing the internal logic. Even calling e.g. `getUserPlaylist` with options for offset/limit it doesn't work as spotify wants to append a `/tracks` to the uri.

kerem commented

2026-02-27 19:25:42 +03:00

Author

Owner

@jwilsson commented on GitHub (Jul 18, 2016):

Hi,
We aim to keep this library as simple as possible and leaving these sort of things up to the user.

I'm not sure if getUserPlaylist was just an example or not, but there's also getUserPlaylistTracks which handles limit/offset. But if you happen to find a method that should support limit/offset but doesn't have it documented, PRs are always appreciated!

@jwilsson commented on GitHub (Jul 18, 2016): Hi, We aim to keep this library as simple as possible and leaving these sort of things up to the user. I'm not sure if `getUserPlaylist` was just an example or not, but there's also `getUserPlaylistTracks` which handles limit/offset. But if you happen to find a method that should support limit/offset but doesn't have it documented, PRs are always appreciated!

kerem commented

2026-02-27 19:25:42 +03:00

Author

Owner

@andig commented on GitHub (Jul 18, 2016):

I wasn't even aware of getUserPlaylistTracks, thank you!

@andig commented on GitHub (Jul 18, 2016): I wasn't even aware of `getUserPlaylistTracks`, thank you!