Replies: 1 comment 3 replies
-
Yeah the APIs to do this are in there but I guess they aren't exposed. Mostly because of the short life of the cache on forward navigation. I was thinking we wouldn't need to invalidate anything manually that we weren't also refetching since odds are by the time you do the next thing, things would have changed. I guess when I changed the behavior I think in 0.13.x to persist as long as the data is already on the page changed that assumption. Because now we don't fetch it again if it is already on the page, and that is something invalidating would allow for. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Currently the API only has a method to instantly
revalidate
caches. In some cases it would be useful to be able to just clear the cache without triggering the reload. Thinking of this situation: "You know that some data in the cache is old/invalid, but you don't already need the new data".Beta Was this translation helpful? Give feedback.
All reactions