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 reporting is null on the client side. #17

Closed
jlengstorf opened this issue Oct 16, 2017 · 0 comments · Fixed by #20
Closed

Error reporting is null on the client side. #17

jlengstorf opened this issue Oct 16, 2017 · 0 comments · Fixed by #20
Labels

Comments

@jlengstorf
Copy link
Member

Whenever an error happens in a query, the log is correct on the server, but shows up null on the client side.

@jlengstorf jlengstorf added the bug label Oct 16, 2017
jlengstorf added a commit that referenced this issue Oct 16, 2017
- Pre-call formatError with a logger to avoid confusion. This is important, because I confused myself and spent two hours accusing the Apollo team of changing the API before I realized what I’d done.

- Improved error reporting for GraphQL core error (e.g. syntax errors). Messages are no longer swallowed on the client side.

fix #17
jlengstorf added a commit that referenced this issue Oct 16, 2017
jlengstorf added a commit that referenced this issue Oct 16, 2017
- Pre-call formatError with a logger to avoid confusion. This is important, because I confused myself and spent two hours accusing the Apollo team of changing the API before I realized what I’d done.

- Improved error reporting for GraphQL core error (e.g. syntax errors). Messages are no longer swallowed on the client side.

fix #17
jlengstorf added a commit that referenced this issue Oct 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant