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

Error handling #685

Open
Pim-Infuzed opened this issue Dec 4, 2023 · 1 comment
Open

Error handling #685

Pim-Infuzed opened this issue Dec 4, 2023 · 1 comment

Comments

@Pim-Infuzed
Copy link

Hi,

As a happy user of your graphql library I have one request.
If runtime error occurs in graphql.Do or any of the solvers involved, it is really hard to find where this vulnerability occurs because most of the information is lost somewhere.
Is there a way to prevent this los of information?

@pyropy
Copy link

pyropy commented Dec 28, 2023

I am having the same issue. Having stack trace returned together with the runtime error would be helpful, or some flag that would let program panic and crash (at least for development purposes)

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