Order of MutationCache.onMutate

[Xiot]

Is there a way to have the MutationCache.onMutate handler called after the specific onMutate function from the mutation?

From poking around I see that the order looks something like

MutationCache.subscribe({type: 'added'})
MutationCache.config.onMutate
mutation.onMutate
mutation.mutationFn

I'd love to be able to have a way to inject something that runs between mutation.onMutate and mutation.mutationFn, preferably without having to modify the mutation.mutationFn.

The reason being, is that I want to be able to capture the context returned from the mutation.onMutate call.

The reason that I'm trying to accomplish this, is that my API has a fairly standardized response pattern, and I also have some specialized ways to build up the mutation options.
I'm trying to use this to my advantage for optimistic updates and just have the mutation.onMutate say how it should mutate various query keys but the actual setQueryData calls will be done in a single place.

Since I do have an abstraction already in place to create the mutation options, I could just place the handler within the mutationFn, but that would require a separate event to be fired and handled outside of RQ

[Xiot]

Actually, taking a deeper look through the emitted events, it does look like there is a pending event that is fired. Once before, and once after the mutation.onMutate method is called.

// MutationCache.subscribe event = { type: 'updated', action: { type: 'pending', ...} }
// mutation.onMutate
// MutationCache.subscribe event = { type: 'updated', action: { type: 'pending', context: <returned context>, ...} }
// mutation.mutationFn
// MutationCache.subscribe event = { type: 'updated', action: {type: 'success', ... }

This should be what I need