feat(openapi-react-query): Type-safe setQueryData #2430
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.
Changes
Add
setQueryData
helper toopenapi-react-query
for type-safe setting of query data as discussed in #1806, as proposed by @ShoeBoemI think a typesafe
invalidateQueries
is also a nice addition, and I'd be more then happy to add it to this or a new PR.Disclaimer:
I have used AI in the making of this PR to understand, research and document the feature (GPT 4.1). I have validated the results myself and am satisfied with code quality, tests and type safety and feel confident that this is a nice step forward for the package.
How to Review
I've added an example project to play around with the typesafety of the
setQueryData
function on the api client.Checklist
docs/
updated (if necessary)pnpm run update:examples
run (only applicable for openapi-typescript)