Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
revert #1938
After new mutate API is landed, we're able to clear the cache or partially set cache with it, like
mutate((key) => filter(key), data)
. We encourage users to usemutate
API instead of manipulate cache provider itself directly.Origin Problem
Previously users are struggling with typing with cache provider, and trying to call
cache.clear()
, which might result into inconsistence between cache provider and react state in swr. So we introduce the new mutate API to let users manipulate cache easily. The type generics foruseSWRConfig<CacheType>
is a bit redudant if you really want to forcedly type a returned cache from context. You can just useas
type guard like below:By default the cache type is
Cache<any>