(core) - Fix mutation operation's identity being used for filtering results

[mlecoq]

I'm trying to use urql to make a mutation but no result is returned

urql version : 2.1.1

Steps to reproduce

I have made a small example to reproduce the issue here : https://github.com/mlecoq/urql-issue

It is a simple login form that calls my login mutation to log in

Expected behavior

I expect to have a result after calling it

Actual behavior

I see with flipper that the network call is made but the promise never returns

[kaleabmelkie]

I got the same issue after upgrading @urql/core to 2.4.0 in a Svelte app too. The following promise does not resolve or reject, although the request was actually sent and was completed (I saw that in the dev tools Network tab).

const { data, error } = await client
    .mutation(LoginDocument, { input })
    .toPromise()

Also, I've noticed this happens only when used with either cacheExchange or authExchange for some reason. Removing both makes the promise resolve (I use basically every other officially supported exchange in my setup, but none of them cause this issue).

[JoviDeCroock]

Hey. we've identified the issue and will get a fix out asap

[mlecoq]

Thanks a lot for your speed !

[kitten]

No worries 👍 This should be resolved in @urql/[email protected]. Sorry for the regression 😄