Include GraphQL operation name in the unhandled request warning

[vldslv-a]

Scope

Adds a new behavior

Compatibility

• This is a breaking change

Feature description

Hello! Previously, in unhandled graphql request errors, you could see the operationName of the query, but at the moment this is not possible. Could you provide an example or a function that would fix this?

[kettanaito]

Hi, @vldslv-a. Thanks for letting us know.

We've removed the parsing of requests from the onUnhandledRequest logic because it's expensive and everybody was paying for it, even if they aren't using GraphQL (there's no way of knowing if a request is a GraphQL request until you attempt to parse it).

I am a bit hesitant to add the parsing back, even if behind an option (not a fan of configurations in general).

Would it be more helpful if we instead printed a stringified request body in the message?

[MSW] Error: intercepted a request without a matching request handler:

  • POST https://app/graphql
    {"query":"query GetUser { ... }","variales":{...}}

Reading the request body is not as expensive and will include the GraphQL request information to help you identify the unhandled request. Let me know!

[vldslv-a]

Would it be more helpful if we instead printed a stringified request body in the message?

Yes, that would be nice! It would at least give us more information about unhandled requests, because sometimes they are hard to find.

[kettanaito]

@vldslv-a, if you are interested, you can open a pull request with this change! I will help you review the code and merge it for everyone to use.