Get mutation observer by key using query client

[imaksp]

Hi, how can I get mutation observer by mutation key using queryClient. I want to call mutation reset method from different component.
I could get it from client.getMutationCache().find({muationKey: 'key'}), but it won't have reset method.
I am using this with Angular.

[TkDodo]

I want to call mutation reset method from different component.

can you elaborate on your use-case?

[imaksp]

Hi, I have global modal dialog component which displays elements based mutation status, and it also has cancel button, but I don't want to pass mutation object around, so I was thinking about passing mutationKey, add calling reset on cancel click. basically I want to reset mutation status to idle and clear errors (if any).

[TkDodo]

you can’t cancel a mutation, it’s not a query. Mutations are pretty much “fire-and-forget”, and you can observer it’s state with useMutationState.

Whenever you call mutate(), we create a new mutation that has nothing to do with any other mutations, even if they have the same key. Mutations don’t work like Queries.

useMutation observes the last instance of when mutate() was called, so reset just “unobserves” it, that’s why you get back to an idle state. But it doesn’t “cancel” anything:

query/packages/query-core/src/mutationObserver.ts

Lines 102 to 109 in 75131d6

	reset(): void {
	// reset needs to remove the observer from the mutation because there is no way to "get it back"
	// another mutate call will yield a new mutation!
	this.#currentMutation?.removeObserver(this)
	this.#currentMutation = undefined
	this.#updateResult()
	this.#notify()
	}

[imaksp]

Hi, I know that it won't cancel anything, but in this case its web3 txn call, and cancel/close button will appear after some timeout, and I only want to reset its status to idle (reset method). its ok if it doesn't cancel any http call, actually user can also cancel it from wallet app and our app will get callback and mutation will fail and dialog will display Failed correctly.
but this is for handling some rare case, to allow explicit cancel/force close after timeout, it is needed as this dialog won't have close button. if its not possible (as observer is private field) will find some workaround.

[TkDodo]

even if you had access to the reset method from the observer, it would only reset the state of the observer. The mutation itself would never go back to idle state. sorry, mutations aren’t really made for global state sharing like this.

[imaksp]

Hi, no worries, will find another way, and thank you for maintaining such a great lib. 😊