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
It would be really useful to invalidate the cache automatically for queries that depend on the updated data and have the same __typename.
Example:
item with __typename Book gets deleted -> refetch query with list of books
That topic was already previously talked about: (#58 (comment))
[...] Would you want a way to automatically trigger refetches of the deleted value or is that something you would do by hand? Or just the next time the query is fired?
I really like this idea and it piggy backs on the exact same infrastructure that we need to do #1225. If this is something you have the time/energy to take on let me know - it should be a fun one.
Describe the feature
It would be really useful to invalidate the cache automatically for queries that depend on the updated data and have the same
__typename
.Example:
__typename
Book gets deleted -> refetch query with list of booksThat topic was already previously talked about: (#58 (comment))
It would be nice to have a similar functionality what urqls GraphCache provides:
https://commerce.nearform.com/open-source/urql/docs/graphcache/normalized-caching/
Another thing to keep in mind is how we could invalidate the SvelteKit load functions automatically whenever a GraphQL mutation gets triggered.
Criticality
cool improvement, my projects will benefit from it
The text was updated successfully, but these errors were encountered: