Skip to content
Discussion options

You must be logged in to vote

@jonathanstanley, after some research, found out that this breaking change has been introduced with the upgrade to graphql-js^16, which dropped support for # [...] descriptions in schemas (the GraphQL spec has also been updated on this matter)
The new spec states that:

  • # [...] syntax is used for comments (which are not collected as descriptions)
  • " [...]" and its multiline counterpart syntax should be used for descriptions (which are collected by codegen for TS comments)

Replies: 2 comments 6 replies

Comment options

You must be logged in to vote
4 replies
@jonathanstanley
Comment options

@charlypoly
Comment options

@charlypoly
Comment options

@jonathanstanley
Comment options

Comment options

You must be logged in to vote
2 replies
@jonathanstanley
Comment options

@jonathanstanley
Comment options

Answer selected by charlypoly
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants