[
https://issues.apache.org/jira/browse/SLING-10502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17368876#comment-17368876
]
Julian Sedding commented on SLING-10502:
----------------------------------------
[~bdelacretaz] I think it's fine if you gather some experience with these
utilities in the GraphQL module. It would be nice to eventually see something
like it in Sling API, but there's no rush IMHO.
> Helpers for lazy loading of GraphQL query results
> -------------------------------------------------
>
> Key: SLING-10502
> URL: https://issues.apache.org/jira/browse/SLING-10502
> Project: Sling
> Issue Type: Improvement
> Components: GraphQL
> Affects Versions: GraphQL Core 0.0.10
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Priority: Minor
> Fix For: GraphQL Core 0.0.12
>
>
> Lazy loading of "expensive" field values can help the performance of GraphQL
> queries, by omitting calls to methods that retrieve or compute data if the
> corresponding fields are not used in the result set.
> A natural way of doing that is to return a {{Supplier<SomeType>}} instead of
> {{SomeType}} directly. I'm not sure if the GraphQL Core supports that
> correctly out of the box, it would be good to try that and maybe implement
> the corresponding improvements.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
