[
https://issues.apache.org/jira/browse/SLING-10375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17345972#comment-17345972
]
Bertrand Delacretaz commented on SLING-10375:
---------------------------------------------
I took the liberty of changing this ticket's title to "Sling-specific GraphQL
directives should be built in" which I think better expresses the intention.
I haven't looked at the PR code so far but what's the plan for backwards
compatibility? We should make sure existing schemas which include definitions
for these directives continue to work.
> 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)
