GraphiQL expects 200 status for errors

[graphql]

GraphiQL expects 200 status for errors

[sporto]

hi @asiandrummer using graphiql 0.5 this is the behaviour I see.

Consider a query where one attribute doesn't exist e.g. unknown in the screenshot below

In this case I have setup my graphql server to return a 200 with the errors. GraphiQL shows the error on the right panel.

But returned 200 when an error happens is not what we think should happen.

So in the screenshot above I have set up the server to return 422 with the error. GraphiQL just shows [object Object] on the right.

The expected behaviour would be to have GraphiQL show the error on the right if there is an error on the response body, even if the status is 422.

[asiandrummer]

Hi @sporto - sorry it took a while to get to this. I'm not sure if I understand the problem; when you say "bad queries", do you mean a invalid query with a correct syntax (e.g. a field that isn't defined is queried), or a query that returns null because the result was empty?

GraphiQL does not know about the network status/http status code/etc - instead it handles errors if the defined fetcher rejects the query and/or an error is thrown during the execution (defined here). So it is possible to render the error logs without a specific status code - express-graphql implementation is an example of this.

[asiandrummer]

I see. Just checking in case - is your server throwing an error whenever it comes across any responses other than 200 status? The query execution workflow is set up so that the response (in your case maybe a JSON.parsed object?) gets passed into the callback defined in _runEditorQuery function in GraphiQL component, and if there's any error thrown from the fetcher, _fetchQuery will catch the error and try to find a stack trace, or cast the error into String format, which is what I think might be happening with your 422 status code:

  _fetchQuery(query, variables, cb) {
    this.props.fetcher({ query, variables }).then(cb).catch(error => {
      this.setState({
        isWaitingForResponse: false,
        response: error && (error.stack || String(error))
      });
    });
  }

FYI, our example fetcher definition does this from example/index.html:

try {
  return JSON.parse(responseBody);
} catch (error) {
  return responseBody;
}

[sporto]

@asiandrummer I don't follow your question, can you please rephrase it?
As far as I can tell my server is returning exactly the same (headers and body) but the only thing that is different is the status code.

[asiandrummer]

is your server throwing an error whenever it comes across any responses other than 200 status?

Sorry; what I meant was a "client-side fetcher code", not a "server". I was just curious how your fetcher is defined.

[sporto]

I see this error:

I see what you mean about the fetcher, I'm using axios, so you are saying that the error is most likely happening there? I will investigate this.

This is how it is defined at the moment:

import 'graphiql/graphiql.css'

import React from 'react'
import ReactDOM from 'react-dom'
import GraphiQL from 'graphiql'
import axios from 'axios'

function graphQLFetcher(graphQLParams) {
  return axios({
    url: '/graphql',
    method: 'POST',
    data: graphQLParams,
  })
}

ReactDOM.render(<GraphiQL fetcher={graphQLFetcher} />, document.body)

[sporto]

Ok, that is the problem, thanks so much for helping debug this. Closing this issue.

[asiandrummer]

:D glad you were able to resolve the issue - awesome!