New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

endcursor fail with duplicate publishdate on quering products #860

Open

Whitebytes opened this issue May 21, 2024 · 0 comments

Whitebytes commented May 21, 2024 •

edited

Loading

Describe the bug
duplicate publishdates will result in:
"hasNextPage": true,
"endCursor": null

true indicates the excitence of a next page, but quering the "null" endcorsor brings you right back at the start of pagination.

duplicate publishdates are easely made with the bulkeditor, so we have them a lot.

To Reproduce
Steps to reproduce thae behavior:

Make 2 publisdates the same
query products, like:
query productsQuery(
$where: RootQueryToProductUnionConnectionWhereArgs,
$after: String){
products(first: 200, after: $after, where: $where) {
pageInfo{
hasNextPage,
endCursor
}
edges{
cursor
node{
name
}
}
}
}
{"where":{"categoryIdIn":[1623],"orderby":[{"field":"DATE","order":"ASC"}]}, "after":"YXJyYXljb25uZWN0aW9uOjI0MjgzMg=="}

Expected behavior
values:
"hasNextPage": true,
"endCursor": null
should never coexcist.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment