Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Status codes for non-fatal properties
See original GitHub issueI just ran into an issue while using Apollo Client with Hasura. Since Hasura always returns a 400 status code when there’s an error in the query, Apollo Client will always treat that error as a networkError and not pull the graphql errors out of the response.
Apollo client expects a query with non-fatal errors (it seems like that means if there’s a query with optional fields that fail) to return as a 200 with the errors property instead of the data property.
Can the status codes be changed in Hasura to have full compatibility with Apollo Client?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
The new
/v1/graphqlwill have this behaviour. Will be part of the next release.The GraphQL spec doesn’t say anything about the transport layer and the HTTP best practices section on graphql.org doesn’t talk about status codes. I think the only sane option left is to check what the most popular graphql clients expect and decide based on that? @coco98 @shahidhk