Uh oh!
There was an error while loading. Please reload this page.
Add support for checkpoint based pagination when fetching a list of clients - #746
Conversation
tanya732
commented
Aug 13, 2025
Hi @PhillipTr01 You’re right, currently the SDK doesn’t support checkpoint pagination properly because the next value isn’t set automatically when using q, from, and take. Overriding the constructor and extending to set those parameters manually works. That said, there’s a minor refactoring in progress that will affect this endpoint. Once that lands, I’ll update the SDK to reflect the changes (including those related to this endpoint). I’ll keep you posted as things move forward. Thanks again for raising the PR !! |
PhillipTr01
commented
Sep 17, 2025
Hey @tanya732, are there any updates on this pull request :)? |
tanya732
commented
Apr 9, 2026
Hi @PhillipTr01 There is an open proposal to support checkpoint pagination, but we don’t have a concrete ETA to share at this time. Thank you for the cooperation. |
Changes
Based on the documentation it is possible to use the Query Parameters
q,takeandfromfor checkpoint based pagination. The problem was that the library doesn't support this yet. Thenextvalue won't be set. Overriding the existing constructor with one that sets thenextparameter fixes this.Testing
There is currently no test suite for checking if pagination is working. Manual Testing is possible by creating a ExtendedClientFilter (in my case i tested it with Kotlin) in your application:
Calling the
.clients().list()function returns thenextvariable in the body.Checklist