Support for string literals as description

[kortac]

As of version 0.12.3 the default style of describing a type or field is to add a string literal instead of a comment.
https://github.com/graphql/graphql-js/blob/master/src/utilities/extendSchema.js#L44

Expected Behaviour

Parsing a schema with string literals as descriptions and generating the Golang files.

Actual Behavior

Crashing due to invalid syntax.

Minimal graphql.schema and models to reproduce

"This is a description."
schema {
    query: Query
}

Results in unable to parse schema: graphql: syntax error: unexpected "\"This is a comment.\"", expecting Ident (line 1, column 1)

[imiskolee]

maybe start with comment symbol is better. like

//This is a description.
schema {
    query: Query
}

[kortac]

gqlgen should stick to the reference implementation.

The implementation states that descriptions should be written as string literals. Comments are no longer used for descriptions.

/**
 * Descriptions are defined as preceding string literals, however an older
 * experimental version of the SDL supported preceding comments as
 * descriptions. Set to true to enable this deprecated behavior.
 *
 * Default: false
 */
commentDescriptions?: boolean,

Source: https://github.com/graphql/graphql-js/blob/master/src/utilities/extendSchema.js#L44

[imiskolee]

@SpaceHeroGuide got it. thanks!

[vektah]

The blocker on this, and a few other issues is the parser we use for schema.

Upstream issue graph-gophers/graphql-go#196

Another alternative is to fork https://github.com/tmc/graphql and get it up to date. A parser generator would be nice way nicer to work with than a hand rolled parser.

[vektah]

Fixed in 0.4.0