feat: New usePrepare<Op> hook to enable reactQuery.useQueries #233
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.
The feature I'm looking for is to have a type-safe reliable way to use
useQueries
.I thought about using ReactQueryFunctions instead of ReactQueryComponents. However, having a mix of both (see #232) is not ideal and causes to have a whole lot of duplicated code.
Since I prefer the hook approach, I wanted a way to make this work.
In the current state it is impossible to extract all the goodies provided by the
use<Op>
hook, namely theuseContext
, thequeryKey
andqueryFn
.My proposed solution is to make a new hook call
usePrepare<Op>
that returns a function (factory) to then create the queryKey/queryFn from variables.I'm open to suggestions on naming, not totally sold on it
This is the end result I'm looking for in my app