I have a GraphQL query which looks like so

query Person($cursor: ID, $limit: Int) {
  items:{
     ...
  }
  name
  ...
  cursor
}

While making the query for the next page, I fetch using the returned cursor.

However, the user can also mutate these items. Let’s say the user deletes an item. I can use either writeFragment or cache.modify directly to delete it from the array. But the trouble occurs when I need to fetch more data.

From what I’ve noticed by playing around with the API, the cursor maps to the items. For example, say I delete the 2nd last item. The cursor to fetch more still remains the same. However, if I delete the last item, the current cursor is now invalid.

I’m not even sure if I can rely on this observation but I’m wondering how people implement cursor styled pagination where in the cursor might get invalidated due to mutations. Is there a pattern in apollo which can help this? Is there a good alternative than fetching everything again?

Thanks!