Unexpected error is not useful at all

[Salmandabbakuti]

Sometimes, we do need to report the user(frontend) about the errors like missing auth token, the user does not exist, or bad requests at least in the console. I know that we can configure custom errors by using GraphQLYogaError class, but it doesn't seem to be useful at all as we need to traverse through objects and do conditional checks to display the error messages in the frontend. Why don't we just disable stack trace if it leaks sensitive information instead of showing an unexpected error? or at least log error details in the console for development?

@n1ru4l @saihaj

[n1ru4l]

If you are not happy with how error masking works you can disable error masking and implement your own error handling through a plugin.

import { createServer } from "@graphql-yoga/node"

createServer({
  maskedErrors: false,
  plugins: [
    useYourCustomErrorHandlerPlugin(),
  ]
}).start()

You can learn more about error masking in the tutorial or error masking documentation.

I know that we can configure custom errors by using GraphQLYogaError class, but it doesn't seem to be useful at all as we need to traverse through objects and do conditional checks to display the error messages in the frontend.

In general, I would recommend you model your expected errors as GraphQLObjectTypes using unions and/or interfaces.

There is a great GraphQLWTF episode for this, GraphQL Error Handling with Union Types. I also wrote this article, Handling GraphQL errors like a champ with unions and interfaces, which showcases similar concepts.

[Salmandabbakuti]

Can we atleast log errors in server console(and masking them in clients api response) for debugging in production enviroments with masked errors enabled?

[n1ru4l]

Yes you can do so with the useErrorHandler plugin