RFC: feat(query): add shouldExportMutatorHooks option #1105
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.
Status
HOLD
Description
When client is set as react-query, 3 different functions are generated for each query/mutation. For example:
GOAL: I don't want to export
useCreateUserHook
. This causes confusion for my team and I on which function to use:useCreateUserHook
, oruseCreateUser
? Ideally we always use the react-query version (useCreateUser
), but it's easier if we just don't export it at all, so no one can make the mistake(I arguably don't want
useCreateUserMutationOptions
exported either, but that one is less problematic)I made this an option to preserve backwards compatibility, but let me know your thoughts
Steps to Test or Reproduce
orval.config.js
Verified the mutator hook is no longer exported