Pagination cursor initial value has next page #1201
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.
The current implementation lacks full support for cursor pagination in QueryQL (GraphQL). Issues include the inability to set an initial cursor value for the first query, broken logic preventing cursor field replacement, and flawed exit criteria that ignore the "has next page" condition, potentially causing infinite loops by only checking if the cursor is an empty string.
Pagination Cursor for QueryQL:
The GraphQL cursor pagination documentation:
https://graphql.org/learn/pagination/#pagination-and-edges