[
https://issues.apache.org/jira/browse/SLING-11920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17741219#comment-17741219
]
Andreas Schaefer commented on SLING-11920:
------------------------------------------
I created a PR
[https://github.com/apache/sling-org-apache-sling-graphql-core/pull/36] that
exposed the Object Type Names to the User.
There is also some cleanup and additional tests to verify the proper handling
of Object Type Names.
> Expose Object Type Names in Selected Field
> ------------------------------------------
>
> Key: SLING-11920
> URL: https://issues.apache.org/jira/browse/SLING-11920
> Project: Sling
> Issue Type: Bug
> Affects Versions: GraphQL Core 0.0.20
> Reporter: Andreas Schaefer
> Assignee: Andreas Schaefer
> Priority: Critical
> Fix For: GraphQL Core 0.0.22
>
>
> Intermediary fields are not exposed as Selected Fields in Graphql-java and so
> it was added as list of Object Type Name.
> Now for handling '... on <Type/Model>' we need to expose these Object Type
> Names so that a client can deal with them.
> If we have a query where we have a inline fragments
> ([https://graphql.org/learn/queries/#inline-fragments]) like:
> {code:java}
> {
> image {
> ... on ImageRef {
> type{code}
> Then in the graphql-java 15.0 there is an inlined field called *ImageRef* but
> that is now gone in 20.1. Instead we have a list of Object Type Names in a
> field and in our example *type* would have Objet Type Names:
> {*}["ImageRef"]{*}. So for a client to obtain the type of the inlined
> fragments this data must be exposed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
