[
https://issues.apache.org/jira/browse/SLING-9877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-9877.
----------------------------------------
Assignee: Bertrand Delacretaz
Resolution: Fixed
Thank you for this contribution! I have merged your PR.
> Schema related errors are not captured and returned as a GrpahQL error
> response
> -------------------------------------------------------------------------------
>
> Key: SLING-9877
> URL: https://issues.apache.org/jira/browse/SLING-9877
> Project: Sling
> Issue Type: Bug
> Components: GraphQL
> Affects Versions: GraphQL Core 0.0.6
> Reporter: Jabran Asghar
> Assignee: Bertrand Delacretaz
> Priority: Major
> Fix For: GraphQL Core 0.0.8
>
>
> *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.
>
> [0] [http://spec.graphql.org/June2018/#sec-Errors]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
