We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When searching for 'Drake', the wrapper does not allow a user to continue searching if he has not found his result yet.
It seems that Spotify is using offset pagination as indicated by the href and next keys in the result object:
href
next
{ tracks: { href: 'https://api.spotify.com/v1/search?query=drake&type=track&offset=0&limit=20', items: [ [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object] ], limit: 20, next: 'https://api.spotify.com/v1/search?query=drake&type=track&offset=20&limit=20', offset: 0, previous: null, total: 26505 } }
The wrapper must have a method to continue the search by using the result object's next link.
The text was updated successfully, but these errors were encountered:
Merge branch 'main' into #7-fix-pagniate-bug-when-searching
85704c8
-required to allow reviewer to test branch locally-
Merge pull request #8 from KrishnaSolo/#7-fix-pagniate-bug-when-searc…
b94ca3b
…hing #7 - Added option to allow searching with offset and set limit of items re…
Successfully merging a pull request may close this issue.
When searching for 'Drake', the wrapper does not allow a user to continue searching if he has not found his result yet.
It seems that Spotify is using offset pagination as indicated by the
href
andnext
keys in the result object:The wrapper must have a method to continue the search by using the result object's
next
link.The text was updated successfully, but these errors were encountered: