Feat/add support for cursor key decoder callback #2
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.
We want to use UUIDs for our cursors, whilst they are string formatted for use in URLs and the pagination parameters, they are stored as binary in our database for efficiency. The casting back and forth is ordinarily handled by model casts, but this paginator passes the string value to the database query without casting.
Proposed Solution:
Add the ability to define a callable to decode/deserialise the incoming cursor values before they are passed to the database queries.
Example: