[
https://issues.apache.org/jira/browse/SLING-9479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123925#comment-17123925
]
Bertrand Delacretaz commented on SLING-9479:
--------------------------------------------
I have now added a
[SchemaDescriptionsTest|https://github.com/apache/sling-org-apache-sling-graphql-core/blob/master/src/test/java/org/apache/sling/graphql/core/schema/SchemaDescriptionsTest.java]
to the GraphQL core module.
The
[test-schema.txt|https://github.com/apache/sling-org-apache-sling-graphql-core/blob/master/src/test/resources/test-schema.txt]
now demonstrates how to remove the {{fetch:}} comments from the Schema
Descriptions, while keeping them associated with the desired fields from the
Sling GraphQL Core point of view.
> GraphQL fetcher comments convert to headings in GraphiQL docs
> -------------------------------------------------------------
>
> Key: SLING-9479
> URL: https://issues.apache.org/jira/browse/SLING-9479
> Project: Sling
> Issue Type: Bug
> Components: GraphQL
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Priority: Minor
>
> The GraphQL core currently uses comments like this to map fields to
> DataFetchers:
> {code}
> ## fetch:samples/seeAlso
> {code}
> A common tool to look at those schemas is GraphiQL, which converts such
> comments to headings, considering them to be Markdown.
> We should switch to a less intrusive marker that converts nicely to Markdown.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
