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
We have large lists of entities that we would like the Apollo client to cache. What is the recommended approach to do this?
As I understand... each query to the graph is cached by Apollo (both the entities and the list). How would this work in large lists? Would the client cache each paginated view of data?
What if we queried the list by a different set of parameters (e.g. change sort order), does the Apollo client 'merge' the list of data? Is there a way to do this at all? And what would be a recommended pattern to apply here?
The text was updated successfully, but these errors were encountered:
Since I haven't heard back on this one in a couple weeks, I'm going to close it out. Please feel free to stop by our Spectrum Chat with any further questions. Thank you!
We have large lists of entities that we would like the Apollo client to cache. What is the recommended approach to do this?
As I understand... each query to the graph is cached by Apollo (both the entities and the list). How would this work in large lists? Would the client cache each paginated view of data?
What if we queried the list by a different set of parameters (e.g. change sort order), does the Apollo client 'merge' the list of data? Is there a way to do this at all? And what would be a recommended pattern to apply here?
The text was updated successfully, but these errors were encountered: