There is currently a problem with the relay approach to nested pagination. An example below to illustrate what I mean:
{
"data": {
"locations": {
"edges": [
{
"node": {
"id": "Location_254"
}
},
{
"node": {
"id": "Location_247"
}
},
{
"node": {
"id": "Location_217"
}
},
]
}
}
Here I have 3 locations returned from the request. Now I wanted to break the pages into these places and look at their "history".
query {
locations {
edges {
node {
history(
first:10
after:"eyJzbm9vemVJZCI6Mzg3fQ=="
)
}
}
}
}
This will break down 10 results after the specified cursor. My problem is that this cursor is specific to the location from which it was obtained. The cursor refers to paginate after, applies only to the location from which it came.
Nested pagination attempts to paginate pages at ALL locations here when the cursor actually being used has been grabbed from a specific location.
, , ?
,