Fix pagination cursor retrieval in TidalClient
Updates the method for obtaining the next cursor during track pagination to use the approach from PR #113, retrieving it from 'links.meta.nextCursor' instead of 'meta.nextCursor'. This ensures correct pagination behavior.
This commit is contained in:
parent
6e02aa03ac
commit
fdb9435fbe
1 changed files with 3 additions and 3 deletions
|
|
@ -757,10 +757,10 @@ class TidalClient:
|
||||||
total_fetched += len(batch_tracks)
|
total_fetched += len(batch_tracks)
|
||||||
logger.info(f"Fetched {len(batch_tracks)} tracks in this batch, {total_fetched} total so far")
|
logger.info(f"Fetched {len(batch_tracks)} tracks in this batch, {total_fetched} total so far")
|
||||||
|
|
||||||
# Get next cursor from meta (not nested in links)
|
# Get next cursor using PR #113's approach (confirmed working)
|
||||||
cursor = tracks_page.get("meta", {}).get("nextCursor")
|
cursor = tracks_page.get("links", {}).get("meta", {}).get("nextCursor")
|
||||||
|
|
||||||
# If no next cursor exists, we're done
|
# If no cursor found, we're done paginating
|
||||||
if not cursor:
|
if not cursor:
|
||||||
logger.info("No next cursor found, pagination complete")
|
logger.info("No next cursor found, pagination complete")
|
||||||
break
|
break
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue