transformError was never fully implemented so they are being removed and might come back if they is a real-word use case for them
If you were using the delayLoadingRef util, use the @pinia/colada-plugin-delay instead.
Renaming Error to defaultError allows to differentiate the property from the existing global Error class. Upgrading should be straightforward.

Features

add initial delay plugin (42c8760)
add track and untrack actions for plugins (8902ba3)
allow dynamic values for auto refetches (63d2fd0)
allow extending useQuery return (ef06628)
expose more types (4447d6d)
plugins: pass scope for added variables (a3b666f)
work without the plugin (696f88e)

Bug Fixes

avoid broken reactivity in defineQuery (4c48abc)
dedupe pinia colada (6ace8e8)
keep data if signal is aborted (de5cde5)
pass onMutate context (618312b), closes #95
remove queryCache from mutation hooks (3f1119a)
run create in ssr too (1a6fa4a)
ssr: throw on error in query (58b7f69)
upgrade to new cache format (03e1683)

Code Refactoring

query: remove unused transformError and setup options (de0cb48)
remove delayLoadingRef helper in favor of the plugins (4c9b4cb)
rename the global Error property in TypesConfig to (0021426)

0.11.1

Diff

posva

published 0.11.1 • last month

Changelog

Source

0.11.1 (2024-10-28)

Features

allow refetches to throw on erorr (f168b6c)
allow setting data for unexisting queries (5c3870c)

Bug Fixes

allow gcTime to never be set (4714b9a)
eagerly change asyncStatus on cancel (b2f1349)
staleTime of 0 always refreshes (66ef9ec)

0.11.0

Diff

posva

published 0.11.0 • last month

Changelog

Source

0.11.0 (2024-10-25)

⚠ BREAKING CHANGES

mutations: This wasn't needed as instead, one can use useQueryCache() outside. It could be added back if needed but it's more pragmatic to start without it.
query: The queryCache.cancelQuery() is renamed to queryCache.cancel() to better match the other functions naming. A new function queryCache.cancelQueries() is added to actually cancel one or multiple queries instead of just one.
plugins: In plugins, cache is renamed to queryCache for consistency.
This makes it clearer that queryCache is the result of useQueryCache().

Features

add mutation store (#47) (7954f83)
hmr: warn against bugs (7bb44a0)
nuxt: add auto imports (964bce2)
nuxt: support colada.options (57a0430)
predicate in filter (2fc62b7)
query: add cancelQueries (a374ee2)
run defined mutations in effect scope (86ff5ed)

Bug Fixes

nuxt: plugins (fd95add)

Performance Improvements

tree shake unused stores (e0ede7e)

Code Refactoring

mutations: Remove queryCache from the context (d9c2509)
plugins: rename cache to queryCache (c97639b)
rename caches to queryCache (e514d33)

0.10.0

Diff

posva

published 0.10.0 • 2 months ago

Changelog

Source

0.10.0 (2024-10-04)

⚠ BREAKING CHANGES

useMutation() hooks now uses positional arguments. This change is mainly to simplify migration from TanStack Query.
caches.invalidateQueries() only fetches active queries
The keys option that automatically invalidate keys has been renamed to invalidateKeys and moved to a plugin. This is in practice not needed. It's just an opinionated convenience that can be replaced by directly invalidating queries in the cache with the onSettled() hook in useMutation():

const { mutate } = useMutation({
  onSettled({ caches, vars: { id } }) {
    caches.invalidateQueries({ key: ['contacts-search'] })
    caches.invalidateQueries({ key: ['contacts', id] })
  },
  mutation: (contact) => patchContact(contact),
})