You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Evidently, the way Apollo 3 wants to handle pagination now since it's deprecating the fetchMore call back requires the paginaiton variables be "offset" and "limit". Since neo4j uses "skip" instead of "offset", this will break.
Type definitions
If applicable, add your type definitions to help us reproduce the bug.
To Reproduce
Newst Apollo client... use skip instead of offset... it'll break.
Expected behavior
since apollo is the biggest graphql client, I'd expect neo4j/graphql to accept what they expect as it's kind of a standard.
Describe the bug
Evidently, the way Apollo 3 wants to handle pagination now since it's deprecating the fetchMore call back requires the paginaiton variables be "offset" and "limit". Since neo4j uses "skip" instead of "offset", this will break.
Type definitions
If applicable, add your type definitions to help us reproduce the bug.
To Reproduce
Newst Apollo client... use skip instead of offset... it'll break.
Expected behavior
since apollo is the biggest graphql client, I'd expect neo4j/graphql to accept what they expect as it's kind of a standard.
Here's more:
https://stackoverflow.com/questions/62742379/apollo-3-pagination-with-field-policies
The text was updated successfully, but these errors were encountered: