You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When performing multiple GET requests on an endpoint (Credits) without any sorting, the same unique resource can end up on multiple pages. The total returned resources does not deviate from the inlineCount, concluding that some unique resource is missed while others are duplicated in the result.
By adding a default orderBy on the resource seq attribute, we should be able to avoid this behaviour.
Relevant logs
No response
The text was updated successfully, but these errors were encountered:
The problem
When performing multiple GET requests on an endpoint (
Credits
) without any sorting, the same unique resource can end up on multiple pages. The total returned resources does not deviate from the inlineCount, concluding that some unique resource is missed while others are duplicated in the result.By adding a default orderBy on the resource seq attribute, we should be able to avoid this behaviour.
Relevant logs
No response
The text was updated successfully, but these errors were encountered: