Pagination is broken: next_href does not return cursor

Open
#67 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
api

Research direction

Start by reproducing the /me/tracks response and inspect how the SDK follows the returned next_href URL. Confirm that pagination preserves the cursor parameter, then verify that requesting the next page works with the corrected URL.

Written by the indexing model from the issue text.

Description

I noticed a change in the API response for /me/tracks that took place within the last 2 days. The response returns a collection with a next_href URL, but that URL does not have a cursor parameter, which breaks pagination.

Dominant language
JavaScript
Stars
388
Forks
76
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from soundcloud/soundcloud-javascript

All issues in soundcloud/soundcloud-javascript

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.