useDynamicMutation hook: Getting an error for returned executeMutation function with no variables

[saracodes]

useDynamicMutation hook: Getting an error for returned executeMutation function with no variables

[parkerziegler]

Huh, this is an interesting one and I'm not totally sure what's happening here! Does it give you a specific labelled parameter that it's expecting, or just "label"?

A good thing to note — we're going to be releasing v3.0.0 very soon (likely this weekend), which removes useDynamicMutation altogether. useMutation will function as useDynamicMutation does currently, where variables are applied at execution time — this brings it more inline with how urql works while still preserving the type safety on variables and responses from your GraphQL API.

So, for now, I don't think there's much to do on this end. Especially with standard useMutation as a workaround. I would bet that it may be related to the upstream PPX and how we integrate with the GraphQL query module internals, but since we're moving off of that PPX imminently I don't see too much point in investigating. If we find that similar behavior arises after v3 is released, let's reopen and dive in more. Thanks for using the library and for finding this!

[saracodes]

v3.0.0 🥳
great news!
I will test the code again with the new version and update if it reoccurs.
just for the record, if anyone will need some more details later on -
it didn't expect any specific label, it was just the general error of: This argument cannot be applied without label. and it didn't help to pass some of the optional executeMutation arguments like requestPolicy etc.

Thank you for the detailed reply!