Pagination cursor initial value has next page

[micko189]

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:

• Added support for setting an initial cursor value.
• Implemented functionality for retrieving the has next page.
• Introduced a mechanism to handle iteration exit.

The GraphQL cursor pagination documentation:
https://graphql.org/learn/pagination/#pagination-and-edges

[CLAassistant]

All committers have signed the CLA.

[micko189]

[yesoreyeram]

Hiya. Sorry for the delay reviewing this. Thank you for the valuable contibution. We are looking into this.

Note: We are looking for a generic stop condition implementation that works for all the pagination types. So the review may take bit longer.

[micko189]

Hiya. Sorry for the delay reviewing this. Thank you for the valuable contibution. We are looking into this.

Note: We are looking for a generic stop condition implementation that works for all the pagination types. So the review may take bit longer.

So when the generic implementation can be expected? I know this is in beta, but it is really handy to have this work properly.

[l3eniy]

I would love this feature!

[rn-jernst]

Hiya. Sorry for the delay reviewing this. Thank you for the valuable contibution. We are looking into this.

Note: We are looking for a generic stop condition implementation that works for all the pagination types. So the review may take bit longer.

@yesoreyeram any update on this? I'm running into a cursor issue that is solved by this PR.