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

Schema stitching is swallowing error stacktrace #81

Open
eric-burel opened this issue Nov 23, 2020 · 0 comments
Open

Schema stitching is swallowing error stacktrace #81

eric-burel opened this issue Nov 23, 2020 · 0 comments
Labels
apollo bug Something isn't working

Comments

@eric-burel
Copy link
Collaborator

eric-burel commented Nov 23, 2020

Describe the bug
When an error is triggered by Apollo, we can access the stack trace by digging the Network call. It's not intuitive, but at least it works.

However, merging schemas with graphql-tools will totally change the stack trace, making errors impossible to debug.

To Reproduce

Merge a custom schema with a Vulcan auto generated schema in the starter (we will publish an example of this soon).

Expected behavior

Should give easy access to error stack trace when they happen in a query or mutation resolver, either from client or better, from the server logs.

Context
ardatan/graphql-tools#480
ardatan/graphql-tools#890

@eric-burel eric-burel added bug Something isn't working apollo labels Nov 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
apollo bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant