Closed NfNitLoop closed 2 years ago
Hum,
I'm the 'responsible' for reading the comments. The graphql-java library is.
And according the GraphQL Spec, comments are marked with a #
I'll check that.
But I think it's up to graphql-java:
Did you try to change these comments at the exact same place in the schema, to check if it actually works ?
Etienne
graphql-java still can't read these comments. And it's not a valid syntax according to the GraphQL specifications. I guess that graphql-java will take it into account as soon as the specification does. Then it will be ok for the plug-in.
I close this issue.
The spec does allow for single or double quoted comments. The spec differentiates between #
line comments and "
or """
block comments. The latter is the official way to provide descriptions for types, fields, arguments, etc. Graphql-java also supports single or triple quotes for descriptions and recommends that over the legacy #
comments.
@etienne-sf Can we re-open this and consider supporting quoted comments? It does seem like there's some partial support for """
on types in the plugin but it doesn't seem to work for fields.
Oups I missed this one
Yes, if it's not entirely treated, you can re-open it.
But then I'm sad: I thought it was ok.
Étienne
Unfortunately, I don't have permission to re-open. Can you or @NfNitLoop re-open it?
Your README.md says:
And that does seem to work for
# comments like this
.But I'm working with a schema generated by graphql-js's printSchema function, which outputs:
It would be nice if that were supported too. Though maybe this is just a case of that library doing the wrong thing? (I couldn't find any documentation about using such strings as documentation/comments in GraphQL SDL.)
Thanks for this library!