pollInterval not working with offset-based fetchMore pagination

I’m using fetchMore to implement offset-based pagination as suggested in the docs, and that works. But when I add pollInterval to refresh the data, it wipes out all the newly loaded data every time the interval triggers.

What am I doing wrong?

[smeijer]

Wouldn’t this issue actually be solvable when a poll used an updateQuery similar to fetchMore? If updateQuery had a parameter that told us if it was triggered by a poll, or a fetchMore request, we could update the prevResult with fetchMoreResult / pollResult accordingly.

[kadikraman]

I have an infinite list that uses fetchMore, but needs to be polled for items (think twitter). So basically same problem as y’all. This is how I solved it:

My API is already implementing the cursor approach where I send the id of the latest item and it’ll give me the next 10.

1. added a param firstItemId to my api where instead of sending the next 10, it returns all newer items
2. added a query, nested inside the original paginated query that just polls the list with firstItemId every 2 seconds
3. use onCompleted to manually add the new items to the cache

So far it works. I can’t quite decide if it’s a clever solution or just a giant hack. Maybe it’s both 😄

@smeijer 's suggestion would 💯 fix this problem. Hope it gets implemented some time!