Skip to content

Commit 9cbd5f2

Browse files
authored
Add note about not including "next" field when limiting fields and using pagination (JohnnyCrazy#962)
1 parent 7bdaf06 commit 9cbd5f2

1 file changed

Lines changed: 5 additions & 0 deletions

File tree

‎SpotifyAPI.Docs/docs/iplayableitem.md‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -54,3 +54,8 @@ By requesting just the track name from the items, we don't have any kind of type
5454
playlistGetItemsRequest.Fields.Add("items(track(name,type))");
5555
```
5656

57+
If you're paginating a request with a subset of fields and you don't include the field `next`, we assume there is only one page and your results will be limited. To fix this, you must include `next` as one of the fields:
58+
59+
```csharp
60+
playlistGetItemsRequest.Fields.Add("next, items(track(name,type))");
61+
```

0 commit comments

Comments
 (0)