우빈

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...

Sorry, I fix error that 'should not allow excess properties' test don't have assertions

Thank you, @andredewaard. I'm not sure if I understood it correctly, but it seems like this can basically be implemented using the spread operator. I’ve used a similar pattern when...

To override queryOptions without using the spread operator twice, you can use a prop getter. ```jsx const compose = (...functions) => (...args) => functions.forEach((fn) => fn?.(...args)) const options = queryOptions({...

I find mutationOptions useful. Currently, I am using a style that manages queryKeys and mutationKeys by bundling them into javascript objects, and mutationOptions can reduce developers' type mistakes and boilerplate...

I fixed the part where the test code was incorrect and added test code to check that useMutation works properly when there is no mutationKey.