-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for descriptions #33
Comments
Relates to graphql/graphql-spec#420 |
I have since implemented a new parser which handles the descriptions correctly so this is not an issue for me anymore. Please reopen if you want to track this as a feature request. |
Yes, I want to track this issue. |
We are also running into this issue, what would the steps be in adding support for this? |
Just as usual - PR, review, merge, publish, update dependent projects. |
Also see #124 :
|
@sungam3r At a minimum, we should ignore description fields, even if for a later version we actually parse them. I would say this should be done for 4.0 if we have the time. (Ok to release 4.0 now though; this can always just be an updated version of the parser engine, and we can release 4.0.1 to use the new parser.) |
Support for descriptions was added in #132 |
So 4.0 added support for comments but it seems that comments should be ignored by the parser. Descriptions are what the spec uses for documentation. More here graphql/graphql-js#927 and here https://graphql.github.io/graphql-spec/June2018/#sec-Descriptions
The text was updated successfully, but these errors were encountered: