How to properly render from "cache" without useQuery

[lucax88x]

Hard question to write, but easy to show if I expose a "classic" use case.

Let's suppose:

• I have an useQuery where I fetch my todos
• I have a mutation, like "markTodo", thanks to the graphcache it will automatically "rerender" the list of todos without fetching graphql again (which is something I actually love)

Now, I'm in a position where I cannot use useQuery anymore, because I have 1 milion todos and I have to implement an infinite scroller, therefore, I'll use useClient and perform manual queries with pagination.

Suddenly, my mutation will update the cache, but my todo will not rerender again, because I have nothing that listen to the cache change like useQuery was doing.

I have several ideas, but nothing that makes me happy, how I can achieve what useQuery was doing?

[JoviDeCroock]

Instead of using a promise you should open a subscription with the help of the wonka library which the react library uses under the hood. However why would you not use useQuery, pagination can still be used like this example https://github.com/FormidableLabs/urql/blob/main/examples/with-pagination/src/PaginatedNpmSearch.jsx

[lucax88x]

Interesting example, so, basically you are rendering an use query for each page, makes sense, thanks!!