-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
feat(react-query): add mutationOptions #8960
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
feat(react-query): add mutationOptions #8960
Conversation
5e14207
to
596896d
Compare
View your CI Pipeline Execution ↗ for commit f3b74c0.
☁️ Nx Cloud last updated this comment at |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sorry but it seems like you’ve copy-pasted queryOptions and replaced the word query
with the word mutation
:/
your starting point should’ve been useMutation
, not queryOptions
TData, | ||
TMutationKey | ||
>['mutationFn'], | ||
SkipToken | undefined |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
skipToken is specific to queries. This isn’t needed.
UseMutationOptions<TMutationFnData, TError, TData, TMutationKey>, | ||
'mutationFn' | ||
> & { | ||
initialData: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there is no initialData for mutations
TMutationKey | ||
>, | ||
): DefinedInitialDataOptions<TMutationFnData, TError, TData, TMutationKey> & { | ||
mutationKey: DataTag<TMutationKey, TMutationFnData, TError> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we also don’t need a DataTag
, this is query specific.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #8960 +/- ##
===========================================
+ Coverage 44.60% 84.30% +39.70%
===========================================
Files 203 27 -176
Lines 8107 376 -7731
Branches 1815 110 -1705
===========================================
- Hits 3616 317 -3299
+ Misses 4059 50 -4009
+ Partials 432 9 -423
🚀 New features to boost your workflow:
|
Thank you for reviewing my PR. I thought queryOptions and mutationOptions could be structured similarly since it was an options-related function. I re-created useMutation as start. I changed it to only have UseMutationOptions, excluding unnecessary data tags and initialData. |
options: UseMutationOptions<TData, TError, TVariables, TContext>, | ||
): UseMutationOptions<TData, TError, TVariables, TContext> | ||
|
||
export function mutationOptions(options: unknown) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if there’s only declaration, we don’t need overloads
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, I changed it to a non-overloaded function.
I merged #9094 to resolve below ci failure because of flaky timer tests ![]() |
mutationOptions helps extracting mutation options into separate functions.