[SLING-9877] Schema related errors are not captured and returned as a GraphQL error response

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: GraphQL Core 0.0.6
• Fix Version/s: GraphQL Core 0.0.8
• Component/s: GraphQL
• Assignee: Bertrand Delacretaz
• Reporter: Jabran Asghar
• Created: 04/Nov/20 13:42
• Updated: 09/Nov/20 10:49
• Resolved: 05/Nov/20 09:30

Description

Problem:
GraphQL query execution problems are captured by SLING-9847 and SLING-9870, but errors which may occur due to schema being not valid (for any reason), are still not captured. In such cases, a non standard error response is sent back to client.

Proposed solution:
Capture the errors, and format it according to GraphQL error response specification [0]. Utilize "extensions" JSON property to capture any additional meaningful information.

PR: https://github.com/apache/sling-org-apache-sling-graphql-core/pull/14

 

[0] http://spec.graphql.org/June2018/#sec-Errors