GraphQLBundle icon indicating copy to clipboard operation
GraphQLBundle copied to clipboard

Backtraces of exceptions thrown in resolvers

Open inwaar opened this issue 5 years ago • 0 comments

Q A
Bug report? yes
Feature request? no
BC Break report? no
RFC? no
Version/Branch 0.13.4

Having the following config:

overblog_graphql:
  ...
  errors_handler:
    map_exceptions_to_parent: true
    exceptions:
      errors:
        - "Throwable"
      warnings:
        - "ProjectNamespace\\WarningException"

there is a weird backtrace that doesn't show any traces from a resolve method which makes it almost useless...: image

If I comment out map_exceptions_to_parent I get the full backtrace but the message Internal server Error. image

Is there a way to get the original message as message (not debugMessage) from any exception and correct backtrace at the same time?

inwaar avatar Nov 21 '20 18:11 inwaar