Expose internal methods used to create query options #343
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
timostamm
reviewed
Feb 26, 2024
srikrsna-buf
approved these changes
Feb 27, 2024
timostamm
approved these changes
Feb 27, 2024
This was referenced Feb 27, 2024
Merged
paul-sachs
added a commit
that referenced
this pull request
Feb 29, 2024
## What's Changed * Prevent using extendible input type by @paul-sachs in #345 * Expose internal methods used to create query options by @paul-sachs in #343 **Full Changelog**: v1.2.0...v1.3.0
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.
Ideally we'd be able to create an opinionated version of
useQueriesbut due to the complexity of those recursive types and there still being other queryClient methods that can benefit from these APIs, I propose we expose these internal APIs as helpers.Fixes #333
Fixes #296