connectrpc/connect-query-es (@connectrpc/protoc-gen-connect-query)
### [`v1.2.0`](https://togithub.com/connectrpc/connect-query-es/releases/tag/v1.2.0)
[Compare Source](https://togithub.com/connectrpc/connect-query-es/compare/v1.1.3...v1.2.0)
##### What's Changed
- Add a distinguishing factor between infinite query keys and regular query keys by [@paul-sachs](https://togithub.com/paul-sachs) in [https://github.com/connectrpc/connect-query-es/pull/334](https://togithub.com/connectrpc/connect-query-es/pull/334)
- Add support for enabled to useInfiniteQuery by [@paul-sachs](https://togithub.com/paul-sachs) in [https://github.com/connectrpc/connect-query-es/pull/338](https://togithub.com/connectrpc/connect-query-es/pull/338)
##### Changes to infinite query keys
With [https://github.com/connectrpc/connect-query-es/pull/334](https://togithub.com/connectrpc/connect-query-es/pull/334), we're fixing a bug where the cache of a regular query collides with the cache of an infinite query, which can lead to type mismatches and unexpected failures if you use the same RPC with an infinite query and a regular query.
We are now using a separate query key for infinite queries to solve the issue (we append "infinite" to the key), but this change can potentially affect you:
If you tried to invalidate some infinite queries like `queryClient.invalidateQueries({ queryKey: createConnectQueryKey(...), exact: true })`, this now only invalidates queries initialized with `useQuery`. To invalidate infinite queries, you can either set `exact` to false, or use `createConnectInfiniteQueryKey()` instead. Also note that this change not only affects `invalidateQueries` but any operations against the queryClient that interact with the cache using a key (eg, queryClient.setQueriesData, etc.)
**Full Changelog**: https://github.com/connectrpc/connect-query-es/compare/v1.1.3...v1.2.0
Configuration
📅 Schedule: Branch creation - "before 4pm on friday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
1.1.3->1.2.0Release Notes
connectrpc/connect-query-es (@connectrpc/protoc-gen-connect-query)
### [`v1.2.0`](https://togithub.com/connectrpc/connect-query-es/releases/tag/v1.2.0) [Compare Source](https://togithub.com/connectrpc/connect-query-es/compare/v1.1.3...v1.2.0) ##### What's Changed - Add a distinguishing factor between infinite query keys and regular query keys by [@paul-sachs](https://togithub.com/paul-sachs) in [https://github.com/connectrpc/connect-query-es/pull/334](https://togithub.com/connectrpc/connect-query-es/pull/334) - Add support for enabled to useInfiniteQuery by [@paul-sachs](https://togithub.com/paul-sachs) in [https://github.com/connectrpc/connect-query-es/pull/338](https://togithub.com/connectrpc/connect-query-es/pull/338) ##### Changes to infinite query keys With [https://github.com/connectrpc/connect-query-es/pull/334](https://togithub.com/connectrpc/connect-query-es/pull/334), we're fixing a bug where the cache of a regular query collides with the cache of an infinite query, which can lead to type mismatches and unexpected failures if you use the same RPC with an infinite query and a regular query. We are now using a separate query key for infinite queries to solve the issue (we append "infinite" to the key), but this change can potentially affect you: If you tried to invalidate some infinite queries like `queryClient.invalidateQueries({ queryKey: createConnectQueryKey(...), exact: true })`, this now only invalidates queries initialized with `useQuery`. To invalidate infinite queries, you can either set `exact` to false, or use `createConnectInfiniteQueryKey()` instead. Also note that this change not only affects `invalidateQueries` but any operations against the queryClient that interact with the cache using a key (eg, queryClient.setQueriesData, etc.) **Full Changelog**: https://github.com/connectrpc/connect-query-es/compare/v1.1.3...v1.2.0Configuration
📅 Schedule: Branch creation - "before 4pm on friday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, 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 Mend Renovate. View repository job log here.