Skip to content

Conversation

rafales
Copy link

@rafales rafales commented Feb 11, 2016

While not a perfect solution (it's far from one), this will make working with graphql MUCH better experience as now I'll be able to see what went wrong (at least in case of synchronous code).

@jdugan1024 jdugan1024 mentioned this pull request Mar 23, 2016
@jdugan1024
Copy link

I'd love to see something like this incorporated to help with debugging.

@syrusakbary
Copy link
Member

Closing this issue, as a better error handling had come in the master branch.

@syrusakbary syrusakbary closed this May 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants