Source: thenewstack.io
GraphErrQL Provides Much-Needed Context for GraphQL Errors
The only thing worse than getting an error in response to a query is a vague error response or no response at all. For this, https://thenewstack.io/the-shape-of-things-to-come-graphql-and-the-web-of-apis/ API query language is certainly guilty.
And clear error responses are a good way to find out what’s really going on with the query.
GraphErrQL’s mission is to identify and clearly illustrate issues with GraphQL queries before the application or feature moves into production.
By going to the specific /GraphErrQL endpoint, the developer will have full viewing of the GraphErrQL user interface which shows the query and result.
And clear error responses are a good way to find out what’s really going on with the query.
GraphErrQL’s mission is to identify and clearly illustrate issues with GraphQL queries before the application or feature moves into production.
By going to the specific /GraphErrQL endpoint, the developer will have full viewing of the GraphErrQL user interface which shows the query and result.
Related Articles
Community Partners
DevOps Careers