Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to debug exceptions? #24

Open
brunoreis opened this issue Mar 3, 2017 · 1 comment
Open

How to debug exceptions? #24

brunoreis opened this issue Mar 3, 2017 · 1 comment

Comments

@brunoreis
Copy link

Exceptions are being transformed into graphql error, and this is good. But, is there an easy way to turn this off so that we can see the exception trace to debug errors?

@garte
Copy link

garte commented Apr 7, 2017

We've implemented our own ExecutionContext and overrode the addError class by setting our own class as a parameter named graphql.execution_context.class (simply add this value to the parameters.yml(.dist) and provide a valid class name to use).
You can get the DI container within the addError method via $this->getContainer() and use whatever services you need.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants