GraphQLError does not contains `variables` and `context`. Additional error objects.

[nodkz]

I setup logging GraphQL errors on Sentry.io and got several issues with GraphQLError

1. Determining a type of the error:

RuntimeError (when resolvers throw errors on execution) or InvalidQuery (when provided invalid query). Right now I qualify a type of error via GraphQLError.pathproperty. If it is empty then I got InvalidQuery, if it is an array then RuntimeError.

What do you think about additional Error objects GraphQLRuntimeError, GraphQLInvalidQueryError (inherited from GraphQLError)?

2. Lack of context and variables in GraphQLError

Query I can get via GraphQLError.source.body, but did not found a proper way how to get variables and context.

Diving down to GraphQLError.nodes for obtaining variables is too complicated.

Passing context to formatError when defining express-graphql middleware is possible. But looks weird.

So will be cool if these properties somehow will be added to the GraphQLError.

@leebyron @schrockn what do you think about improving error object?

---

Some examples of error events which I got with my error catch setup for sentry.io

• InvalidQuery example
• RuntimeError example

[kirillgroshkov]

yes, I need it as well!

[samdenty]

For other people facing this issue, graphqlHTTP sends the variables in the params object:

const graphqlHTTP = require('express-graphql');
const {formatError} = require('graphql');

app.use('/', graphqlHTTP(function (req, res, params) {
    return {
        schema: Schema,
        graphiql: true,
        rootValue: {},
        context: buildContext(req),
        formatError: e => {
            const query = params.query;
            const variables = params.variables;
            console.log('Error!', query, JSON.stringify(variables, null, 2));
            return formatError(e);
       }
    };
}));```

[shinaBR2]

Do we have any further solution for Apollo-client?
:(