How to respond with a server error?

[tniezurawski]

Hey folks 👋 I'm struggling with responding with a server error. I use the typical mirage way. Say, I want to simulate 502s and test Apollo's retry mechanism, so under some fake conditions I return this for a query:

return new Response(502);

But what I get returned instead is wrapped in GraphQL error. It looks like miragejs/graphql (or something internally) treats my response with 502 as a regular response and complains that the data is not returned properly:

Is it possible that miragejs/graphql is not aware that it should "re-throw" (pass) the error? Could someone give me pointers on where I should look to fill the gap?

[jneurock]

This is due to how GraphQL itself works. If the GraphQL endpoint is reachable, it wraps errors and includes them in the response. You won’t be able to simulate a 5xx type error by throwing one while resolving a query.

You should be able to override the route handler for the GraphQL endpoint where needed, though:

// Assumes `server` is the instance of the Mirage server
server.post('<path-to-graphql>', new Response(502))

[tniezurawski]

@jneurock Uh, that would be quite global, right?

[jneurock]

It depends on how you’re using Mirage. I thought you mentioned testing and, if you’re using Mirage in a testing context, defining a route handler in a test is not global.