Correct error handling in mutations

[zhulduz]

Hi! Guys, anyone can explain me how I can catch correct errors in mutations?

I noticed that some request can return 200 status, but inside the response has error field with some problem (like Validation Error). I'm a little doubtful how I can catch such errors? no no how I can parse such response, if every mutation has own projection.

mutation SomeAction(...) {
  someAction(...) {
    ...
    error {
      message
      __typename
    }
  }
}

// using
try {
   const response = await someMutation()
   * // Here response could contain error inside `someAction`: response.someAction.error
} catch (err) {
  // catch error with 400 status, for example
}

• • I mean that every mutation has own path to get error object.

maybe I miss something...

[zhulduz]

I know that we can use optional field disableErrorField just to return to standard error flow. But is it possible to apply that flag for every mutation in one place?

Thanks in advance)

[zhulduz]

I found issue here https://github.com/nodkz/conf-talks/tree/master/articles/graphql/errors