[ 
https://issues.apache.org/jira/browse/SLING-10375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bertrand Delacretaz updated SLING-10375:
----------------------------------------
    Summary: Sling-specific GraphQL directives should be built in  (was: 
Explicitly define the supported directives in GraphQL Core)

> Sling-specific GraphQL directives should be built in
> ----------------------------------------------------
>
>                 Key: SLING-10375
>                 URL: https://issues.apache.org/jira/browse/SLING-10375
>             Project: Sling
>          Issue Type: Improvement
>          Components: GraphQL
>            Reporter: Radu Cotescu
>            Assignee: Radu Cotescu
>            Priority: Major
>             Fix For: GraphQL Core 0.0.10
>
>
> The GraphQL Core implementation provides two Sling specific directives:
> # {{@fetcher}} - allows defining which {{SlingDataFetcher}} is used at 
> runtime for a specific field
> # {{@resolver}} - allows defining which {{SlingTypeResolver}} is used at 
> runtime for resolving a specific type
> And with SLING-10309, the {{@connection}} directive will be supported for the 
> Relay specification that provides support for paginating query results.
> Rather than forcing the developers to redefine these three directives in the 
> schemas all the time, it would be better to automatically add their 
> definitions in the generated schemas.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to