At its core, Svelte Query manages query caching for you based on query keys. Query keys can be as simple as a string, or as complex as an array of many strings and nested objects. As long as the query key is serializable, and unique to the query's data, you can use it!
The simplest form of a key is actually not an array, but an individual string. When a string query key is passed, it is converted to an array internally with the string as the only item in the query key. This format is useful for:
// A list of todosuseQuery('todos', ...) // queryKey === ['todos']// Something else, whatever!useQuery('somethingSpecial', ...) // queryKey === ['somethingSpecial']
When a query needs more information to uniquely describe its data, you can use an array with a string and any number of serializable objects to describe it. This is useful for:
// An individual todouseQuery(['todo', 5], ...)// queryKey === ['todo', 5]// And individual todo in a "preview" formatuseQuery(['todo', 5, { preview: true }], ...)// queryKey === ['todo', 5, { preview: true }]// A list of todos that are "done"useQuery(['todos', { type: 'done' }], ...)// queryKey === ['todos', { type: 'done' }]
This means that no matter the order of keys in objects, all of the following queries are considered equal:
useQuery(['todos', { status, page }], ...)useQuery(['todos', { page, status }], ...)useQuery(['todos', { page, status, other: undefined }], ...)
The following query keys, however, are not equal. Array item order matters!
useQuery(['todos', status, page], ...)useQuery(['todos', page, status], ...)useQuery(['todos', undefined, page, status], ...)
Since query keys uniquely describe the data they are fetching, they should include any variables you use in your query function that change. For example:
const queryResult = useQuery(['todos', todoId], () => fetchTodoById(todoId))
The latest TanStack news, articles, and resources, sent to your inbox.