[
https://issues.apache.org/jira/browse/SLING-10502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-10502.
-----------------------------------------
Fix Version/s: GraphQL Core 0.0.12
Resolution: Fixed
I have now merged PR #25,
[https://github.com/apache/sling-org-apache-sling-graphql-core/commit/9a99ba53d0b36a83e3e7814e8be8866b6b15861c]
[~jsedding] I'm not sure where to put this for a more generic Sling variant,
but if we do that later we can always modify the classes from this module to
inherit from the new ones.
> 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)
