-
-
Notifications
You must be signed in to change notification settings - Fork 200
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add documentation about pagination #187
Comments
Please please please Antoine. I had paging sorted with the pre 2.0.0 releases but I'm completely stuck without any clue with this new API. I can see the old version specified cursor and limit parameters in the endpoint requests but can't see anywhere in the 2.x API for these to be passed to the server. |
I have constructed this code snippet that builds on from the example on the main README.md but processes a response's PagedDocumentLinks to obtain more results using a method similar to the pre-2.0.0 releases. Whilst this method works, is this the limit of what's achievable or can it be done in a tidier, more elegant way?
|
This is pretty much how it should work, but it would obviously be much nicer if the SDK supports this out of the box. Feel free to open a PR for that if you're able to make a generic solution. It would be inside |
OK. I have. |
I think we need to create new release that support this pagination 🙏 |
@jeffersonsetiawan yes, good point! Just triggered a new release 🙏 |
The pull request #195 that closed this issue was merged and released as part of Release 2.3.0 🚀 Generated by GitBuddy |
It might not be clear from the get-go how to use pagination support. Adding this to the readme would help implementors!
The text was updated successfully, but these errors were encountered: