Invalidate Apollo cache after mutation *or* vanilla HttpClient?

[mattdsteele]

Similar conversations, but I wasn't able to find a specific answer here: #1486 and apollographql/apollo-feature-requests#5

Our use case: our data updates are split between Apollo mutations, and POST calls using Angular's vanilla HttpClient. In both scenarios, an update could require us to invalidate the query cache.

I can't find a good way to invalidate the Apollo cache, particularly if it's happening outside Apollo's context.

We wouldn't have to get too fancy or surgical with the cache invalidation; even something that invalidates everything in the Apollo cache would be sufficient (our updates are infrequent)

Any suggestions?

[kamilkisiela]

There's a new API for cache in Apollo Angular 2.0 and Apollo Client 3.0, take a look at "Garbage collection and cache eviction". Maybe something interesting for you.