conventions: Does "WithExposedExceptions" work as expected?

I have set:

engine.WithExposedExceptions(false);

but exceptions from resolvers (that are not ExecutionErrors) are still exposed. Specifically, a System.NotSupported exception is exposed as:

{
  "data": ...,
  "errors": [
    {
      "message": "Specified method is not supported.",
      "locations": [
        {
          "line": 3,
          "column": 5
        }
      ],
      "path": [...],
      "extensions": {
        "code": "NOT_SUPPORTED"
      }
    }
  ]
}

I’m returning the result via:

return enging.SerializeResult(result);

What am I missing? How can I prevent exceptions that are not ExecutionErrors from being exposed?

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 15 (2 by maintainers)

Most upvoted comments

it doesn’t seem possible to set those options in graphql-dotnet/conventions

I guessed about it. I have not watched the conventions project yet, although I can roughly imagine what it is. graphql-dotnet gradually evolves and new features appear in it, the reflection of which should somehow appear in consuming projects.