The QueryCache
is the storage mechanism for Svelte Query. It stores all of the data, meta information and state of queries it contains.
Normally, you will not interact with the QueryCache directly and instead use the QueryClient
for a specific cache.
import { QueryCache } from '@sveltestack/svelte-query'const queryCache = new QueryCache()const query = queryCache.find('posts')
Its available methods are:
queryCache.find
find
is a slightly more advanced synchronous method that can be used to get an existing query instance from the cache. This instance not only contains all the state for the query, but all of the instances, and underlying guts of the query as well. If the query does not exist, undefined
will be returned.
Note: This is not typically needed for most applications, but can come in handy when needing more information about a query in rare scenarios (eg. Looking at the query.state.dataUpdatedAt timestamp to decide whether a query is fresh enough to be used as an initial value)
const query = queryCache.find(queryKey)
Options
queryKey?: QueryKey
: Query Keysfilters?: QueryFilters
: Query FiltersReturns
Query
queryCache.findAll
findAll
is even more advanced synchronous method that can be used to get existing query instances from the cache that partially match query key. If queries do not exist, empty array will be returned.
Note: This is not typically needed for most applications, but can come in handy when needing more information about a query in rare scenarios
const queries = queryCache.findAll(queryKey)
Options
queryKey?: QueryKey
: Query Keysfilters?: QueryFilters
: Query FiltersReturns
Query[]
queryCache.subscribe
The subscribe
method can be used to subscribe to the query cache as a whole and be informed of safe/known updates to the cache like query states changing or queries being updated, added or removed
const callback = query => {console.log(query)}const unsubscribe = queryCache.subscribe(callback)
Options
callback: (query?: Query) => void
query.setState
, queryClient.removeQueries
, etc). Out of scope mutations to the cache are not encouraged and will not fire subscription callbacksquery
will be passed as first argument to the callbackReturns
unsubscribe: Function => void
queryCache.clear
The clear
method can be used to clear the cache entirely and start fresh.
queryCache.clear()
The latest TanStack news, articles, and resources, sent to your inbox.