feat: Add offset-based pagination support #3602
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add Offset-Based Pagination Support
Problem
Currently, Kinto only supports token-based pagination which requires sequential access to records. Users cannot jump directly to specific record positions (e.g., records 100-120) without paging through all previous records.
Solution
This PR adds support for
_offsetparameter alongside the existing token-based pagination, allowing direct access to any record position.Changes
_offsetparameter: Allows specifying starting position for recordsKey Features
GET /records?_limit=20&_offset=100returns records 100-119 directlypaginationobject with limit, offset, total, has_moreAPI Examples