TypeSafe Custom GQLError about apollo-server

[glasser]

This sounds like a question about GraphQL, not Apollo Server.

The GraphQL spec specifies the fields message, location, path, and extensions for errors, and discourages the addition of more top-level entries.

That said, GraphQL-level errors aren't the only way to represent erroneous behavior in your graph. If an error is "expected" and should be handled explicitly by your client, it often is better to represent them explicitly in your schema. A common approach is to have fields return a union type that contains both a "successful result" type and one or more error types, which can be differentiated via __typename as you suggest. It's common to use GraphQL-level errors more for "unexpected" issues (eg, schema errors for business logic issues, GraphQL errors for low-level issues).

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
For general questions, we recommend using StackOverflow or our discord server.