Let async-graphql handle cursor encoding/decoding #348
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.
async-graphql's
query
function automatically handles cursor encoding and decoding. This commit removes the custom cursor encoding/decoding code from theslicing
module and uses async-graphql's built-in functionality instead. This change only updates theslicing
module to keep the PR minimal, and a follow-up change will be needed to address the top-levelencode_cursor
anddecode_cursor
functions in thegraphql
module.