Closed defiant214 closed 3 years ago
Cool; thanks for pointing this out.
The response plays API is returning null values for limit and offset in the body, which is not expected. So, in other words, this is a bug in the API itself. I've submitted a ticket to the appropriate team that owns this API.
For context: the client by design sets the limit to the limit returned by the API (if it's present in the response body) and increments the offset by that limit if the limit is present in the response. That is for cases where the requested limit is greater than the maximum limit. This prevents incrementing offset
by more than the actual page size, so that records won't be skipped over.
Backwards-compatible workaround implemented in 4.2.1
Receive TypeError when doing the following