Switch to v2 #479
Merged
Switch to v2 #479
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This adds a function that can apply a static key to a transport, useful when considering SSR contexts where the transport on the client is not the same transport as on the server. --------- Signed-off-by: Timo Stamm <[email protected]> Signed-off-by: Paul Sachs <[email protected]> Co-authored-by: Timo Stamm <[email protected]>
…build/protobuf` (#448)
As discussed in [discussion thread](#449 (comment)), we need to be explicit about cardinality of query keys. --------- Signed-off-by: Paul Sachs <[email protected]>
Signed-off-by: Paul Sachs <[email protected]>
## What's Changed Peer deps update **Full Changelog**: v2.0.0-beta.1...v2.0.0-beta.2 Signed-off-by: Paul Sachs <[email protected]>
## What's Changed This is a release candidate for version 2. **Full Changelog**: v2.0.0-beta.2...v2.0.0-rc.1 --------- Signed-off-by: Paul Sachs <[email protected]>
## What's Changed Fix issue with npm release **Full Changelog**: v2.0.0-rc.1...v2.0.0-rc.2 Signed-off-by: Paul Sachs <[email protected]>
…en when could be passed skipToken (#469) In order to use createQueryOptions with recent versions of react-query and `useSuspenseQuery`, we need to make sure createQueryOptions isn't passing `skipToken` as a potential type when the input type couldn't be skipToken. This is because the typings for `useSuspenseQuery` now disallow skipping (which was always the case, just was not reflected in the types.) To fix this, we overload the `createQueryOptions` call to indicate with it's types that it will only return a skipToken when input is a skipToken. Signed-off-by: Paul Sachs <[email protected]>
…ries (#470) If we customize the queryKeyHashFn, it prevents `queryClient.setQueryData` from finding the query in question, unless the `queryClient` was initialized with the same queryKeyHashFn. It would be nice to be able to customize this on a per query basis but [it doesn't seem to be an accepted approach](TanStack/query#2352 (comment)). --------- Signed-off-by: Paul Sachs <[email protected]>
A dedicated connect-query-core package makes it much easier to integrate non-react integrations. The public API of `@connectrpc/connect-query` hasn't changed at all, all the same methods and types are exposed, we've just separated them into a distinct package that gets reexported from `@connectrpc/connect-query`. This change allows others to depend on connect-query without necessarily depending on react and react-query. Partially addresses #324 --------- Signed-off-by: Paul Sachs <[email protected]> Co-authored-by: Timo Stamm <[email protected]>
paul-sachs
approved these changes
Nov 4, 2024
|
The bot reports 36 commits with missing or unexpected sign-off. I don't think it handles squash-merged PRs properly, and I don't think it would be right if I signed commits authored by others. Since this only merges PRs that have previously passed DCO, I think we're good. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This merges the branch v2 into main, with a note at the top of the README (added in #477):
Important
You are looking at the release candidate for version 2. For the current stable version, see the branch v1.
Related: