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
So I am using fixedCacheKey since two components need to share the same cache for a mutation. But when I unmount all components and re-mount them, the cache is still present. Am I expected to manually reset the cache if I usefixedCacheKey? This feels cumbersome. Is there no way of sharing mutation-cache without having to manually clear the cache?
The text was updated successfully, but these errors were encountered:
Imagine it the other way round - if we did that, we would already have five issues that important data had suddenly disappeared.
If you choose to share mutation data between components, we don't even know if those components will be active at the same time - you opt into handling that data manually by using fixedCacheKey.
So I am using
fixedCacheKey
since two components need to share the same cache for a mutation. But when I unmount all components and re-mount them, the cache is still present. Am I expected to manually reset the cache if I usefixedCacheKey
? This feels cumbersome. Is there no way of sharing mutation-cache without having to manually clear the cache?The text was updated successfully, but these errors were encountered: