chore(deps): update dependency @pinia/colada to ^0.19.0 #187
Reference in New Issue
Block a user
Delete Branch "renovate/v0.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
^0.18.0→^0.19.0Release Notes
posva/pinia-colada (@pinia/colada)
v0.19.0Compare Source
Bug Fixes
Features
BREAKING CHANGES
$nappended to keys for mutations and mutations without a key do not have an artificial key anymore. This is because initially the cache map was a more complex type but with it being a simple Map, there is no point in complexifying the keys. As a result themutationCache.get()now takes the id of the mutation whilegetEntries()work the same. Theexactfilter has also been removed as mutations are, by nature, meant to be called multiple times.0.18.1 (2025-12-11)
Bug Fixes
Features
0.18.0 (2025-12-02)
⚠ BREAKING CHANGES
you were relying on an external signal that aborts within the
query.It used to not set the state by just being an AbortError DomException
and now it will become an error. This behavior is more correct as we
don't want to ignore aborted signals that are external. Each fetch
creates an AbortController and passes the signal to
querywhich isaborted (without a reason) if any other method of the store fetches
again. This is done to avoid using an outdated request.
Bug Fixes
0.17.9 (2025-11-24)
Features
0.17.8 (2025-11-07)
Bug Fixes
0.17.7 (2025-10-30)
Bug Fixes
toCacheKey(#400) (d1d8f3e)Performance Improvements
0.17.6 (2025-09-25)
Bug Fixes
DefineQueryOptions(#388) (22297f0)0.17.5 (2025-09-11)
Features
0.17.4 (2025-09-09)
Bug Fixes
0.17.3 (2025-09-01)
Features
0.17.2 (2025-08-25)
Features
Bug Fixes
0.17.1 (2025-06-13)
Bug Fixes
0.17.0 (2025-06-03)
⚠ BREAKING CHANGES
EntryNodeKeywithEntryKeyEntryKeyTaggedtype now has multiple type params and an array is no longer assignable to it. This is necessary to correctly infer the types forTDataandTDataInitialand if you were manually usingEntryKeyTagged, you will either need to cast arrays to it or useEntryKeyinstead. In most cases this should not affect you. This makes types stricter and also disallows setting a query data toundefined. If you were doingqueryCache.setQueryData(key, undefined), usequeryCache.setEntryStateinstead.Features
Bug Fixes
Code Refactoring
EntryNodeKey(6c7d15b)0.16.1 (2025-05-22)
Bug Fixes
whenrelative to work across timezones (43b4f7d), closes #2930.16.0 (2025-05-21)
This is the biggest release to date! Many bug fixes, typed keys, a lighter and faster build!
⚠ BREAKING CHANGES
queryCache.invalidateQueries()now accepts a second parameter to control whether to refetch or not active queries. It can be set to'all'to force fetch all queries. This replaces the existing behavior of passingactive: null(can be removed now) which wasn't actually working. You shouldn't be negatively affected by this change as it wasn't working previously.queryCache.getEntries()). To achieve this, the hydrated version of the cache has changed.serializeTreeMaphas been removed butserializeQueryCache(which should be preferred) has been kept.EntryNodeKeyandTreeMapNode(internals) have been removed.EntryNodeKeywas juststring | number.toCacheKeyhas been adapted and now returns a plain string rather than an array. This also fixedqueryCache.getEntries(['1'])actually returning entries defined with a numeric key ([1]). The type forkeyis now stricter to ensure everything works well at the type level, you might notice it doesn't allowundefinedas a value (except in objects), this is intended as the serialized version (JSON) transforms it nonull, and will not match in the cache if used, if you want an nullish value, usenull. The documentation has been updated to reflect thisUseQueryEntryExtensionsfromTResulttoTData. Otherwise, this change won't affect you.Features
Bug Fixes
Reverts
Code Refactoring
TResultinto TData (09338a2)0.15.3 (2025-05-06)
Bug Fixes
0.15.2 (2025-05-03)
Bug Fixes
0.15.1 (2025-04-26)
Bug Fixes
0.15.0 (2025-04-18)
⚠ BREAKING CHANGES
change will only affect users directly creating entries with the mutation store
(which should be avoided except in very advanced cases). Given the new
structure of mutation entries and the fact that they are recreated for each
mutation in order to keep a history of mutations, the new process simplifies
things and reduces bundle size. The actions
createandensurein themutation store are now simpler and take less arguments (many were redundant).
Alongside these changes, the mutation store has fixed many subtle bugs.
Features
Bug Fixes
Reverts
0.14.2 (2025-03-26)
Features
Bug Fixes
0.14.1 (2025-03-18)
Bug Fixes
0.14.0 (2025-03-18)
This version introduces codemods to automate migrations 🎉. Try them out with:
You can also globally install ast-grep and run:
Remember to commit changes before running the codemods.
⚠ BREAKING CHANGES
Every global query (
useQuery()anddefineQuery())option passed to
PiniaColadahas been moved to its own optionqueryOptions:You can also use the new codemods to automatically migrate this.
types: This changes allows for Pinia Colada global options to
auto complete but it also requires you to use pass an options object to
app.use(PiniaColada, {}). This is just for typing reasons (it could bea limitation of Vue) but the same old code actually works.
Replace
serializewithserializeTreeMapRemoved
reviveTreeMap(not needed)Removed internal
createdQueryEntryFeatures
Bug Fixes
Performance Improvements
Code Refactoring
0.13.8 (2025-03-09)
Features
0.13.7 (2025-03-04)
Bug Fixes
0.13.6 (2025-02-12)
Features
Bug Fixes
0.13.5 (2025-02-06)
Features
Bug Fixes
0.13.4 (2025-01-31)
Features
0.13.3 (2025-01-14)
Bug Fixes
placeholderData(4c6a3f7), closes #1540.13.2 (2025-01-03)
Bug Fixes
0.13.1 (2024-12-20)
Bug Fixes
0.13.0 (2024-11-26)
⚠ BREAKING CHANGES
null, onlyundefined. This won't affect most use cases and enables better type inference.Features
0.12.1 (2024-11-09)
Bug Fixes
0.12.0 (2024-11-06)
⚠ BREAKING CHANGES
transformErrorwas never fully implemented so they are being removed and might come back if they is a real-word use case for themdelayLoadingRefutil, use the@pinia/colada-plugin-delayinstead.ErrortodefaultErrorallows to differentiate the property from the existing global Error class. Upgrading should be straightforward.Features
Bug Fixes
Code Refactoring
Errorproperty inTypesConfigto (0021426)0.11.1 (2024-10-28)
Features
Bug Fixes
0.11.0 (2024-10-25)
⚠ BREAKING CHANGES
useQueryCache()outside. It could be added back if needed but it'smore pragmatic to start without it.
queryCache.cancelQuery()is renamed toqueryCache.cancel()to better match the other functions naming. A newfunction
queryCache.cancelQueries()is added to actually cancel one ormultiple queries instead of just one.
cacheis renamed toqueryCacheforconsistency.
queryCacheis the resultof
useQueryCache().Features
Bug Fixes
Performance Improvements
Code Refactoring
queryCachefrom the context (d9c2509)cachetoqueryCache(c97639b)cachestoqueryCache(e514d33)0.10.0 (2024-10-04)
⚠ BREAKING CHANGES
TanStack Query.
keysoption that automatically invalidate keyshas been renamed to
invalidateKeysand moved to a plugin. This is inpractice not needed. It's just an opinionated convenience that can be
replaced by directly invalidating queries in the cache with the
onSettled()hook inuseMutation():Features
Code Refactoring
keystoinvalidateKeysand move to plugin (f709928)0.9.1 (2024-09-27)
Features
Bug Fixes
0.9.0 (2024-08-26)
⚠ BREAKING CHANGES
setQueryStateaction has been renamed to
setEntryState.Features
setQueryStatetosetEntryState(f481eb0)0.8.2 (2024-08-21)
Performance Improvements
0.8.1 (2024-08-17)
Features
Bug Fixes
0.8.0 (2024-08-12)
⚠ BREAKING CHANGES
isFetchingfromuseQuery()is renamed toisLoadingto better reflect that it's connected toasyncStatus.The setup option in useQuery now receives the options
as the second argument instead of a context object with the query return
value and the options. This allows the setup function to have a more
predictable signature and makes it easier to type. Only
PiniaColadahas this option, it has been removed from useQuery. Overall, the
option still needs more thinking and will probably change in the future
again.
plugins: The
onSuccess,onError, andonSettledglobalhooks have been moved from
PiniaPluginto a Pinia Colada plugin:PiniaColadaQueryHooksPluginThis feature splits up the
statusstate into twodifferent status properties:
statusis now just for the data'pending' | 'success' | 'error'queryStatustells if the query is still running or not with'idle' | 'running'refetch,refreshand similar methods now resolvethe
stateproperty without rejecting. This is usually more convenient.The
QueryStatustype has been split intoDataStateStatusandOperationStateStatus.the cache store is going through a refactor to empower
plugins. This change shouldn't affect end users unless you are
directly using the cache store.
As a result a lot of the actions have been renamed
refetch -> fetch
invalidateEntry -> invalidate
ensureEntry -> ensure
Their arguments have changed as well.
QueryPlugin. UsePiniaColadainstead.Features
stateproperty touseQueryfor type narrowing (22f3e21)activeproperty to query entry (994db63), closes #65Code Refactoring
isFetchingtoisLoading(003f7a1)0.7.1 (2024-07-30)
Bug Fixes
0.7.0 (2024-07-26)
⚠ BREAKING CHANGES
UseEntryKeytoEntryKeyFeatures
QueryPluginin favor ofPiniaColada(bde53d9)Bug Fixes
Reverts
Code Refactoring
UseEntryKeytoEntryKey(8110feb)0.6.0 (2024-04-02)
⚠ BREAKING CHANGES
UseQueryStatustoQueryStatusmutateno longer returns a promise and catches errorsto be safely used in templates. The old behavior remains the same with
mutateAsyncmutationoption inuseMutation()now onlyaccepts one argument for the variables. This allows to add extra
parameters in the future like a signal, an extra context, etc
Features
Code Refactoring
0.5.3 (2024-02-21)
Bug Fixes
0.5.2 (2024-02-20)
Bug Fixes
0.5.1 (2024-02-19)
Features
Bug Fixes
0.5.0 (2024-02-19)
⚠ BREAKING CHANGES
Features
Code Refactoring
0.4.3 (2024-02-11)
Features
0.4.2 (2024-02-08)
Bug Fixes
0.4.1 (2024-02-07)
0.4.0 (2024-02-06)
⚠ BREAKING CHANGES
QueryPluginto configure useQuery()statusproperty,isPending,isFetchingare now abit different.
Features
Code Refactoring
QueryPluginto configure useQuery() (67cb2d3)0.3.1 (2024-02-03)
Bug Fixes
0.3.0 (2024-02-03)
⚠ BREAKING CHANGES
fetcherforuseQuery()has been renamedto
query. The optionmutatorforuseMutation()has been renamedmutation.Code Refactoring
useQueryanduseMutation(28ecc75)0.2.0 (2024-01-16)
⚠ BREAKING CHANGES
Features
Bug Fixes
Performance Improvements
Build System
0.1.0 (2023-12-25)
⚠ BREAKING CHANGES
Bug Fixes
Code Refactoring
0.0.1 (2023-12-20)
Features
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.