-
Notifications
You must be signed in to change notification settings - Fork 85
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
introspect drops comment new lines which breaks SDL parsing #728
Comments
Seeing this too with a description that terminates in a double quote. 🤔 It's inlined, and makes it so this schema can't be parsed by a Interestingly, whatever process that publishes the sdl to apollo studio on startup seems to be sending/parsing this correctly On the server being introspected, we're running apollo-server@3.1.2 and graphql-js@15.5.1 graphql/graphql-js#1205 in graphql-js seems related but already solved/closed |
This commit introduces `Description` helper to encode top-level, field-level and input-level descriptions. This helps unify some of the description logic we've had across multiple files. This commit also checks whether a description string is a block string character or a string character which then determines whether description needs to be multilined. Fixes #728.
This commit introduces `Description` helper to encode top-level, field-level and input-level descriptions. This helps unify some of the description logic we've had across multiple files. This commit also checks whether a description string is a block string character or a string character which then determines whether description needs to be multilined. Fixes #728. Co-authored-by: Avery Harnish <avery@apollographql.com>
Thanks for the quick turn around @lrlna! |
We had an SDL file on our server-side that looked like:
However
rover graph introspect
turned this into:Which then causes
graphql-js
'slexer.js
to blow up on "unterminated string", i.e. it doesn't like the quadruple quotes.Perhaps this is really a bug in graphql-js's parsing? Being some lazy and filing it here because we found it via
rover introspect
changing the SDL (or maybe that is also happening inside of graphql-js, I'm not sure).I can re-file this with the graphql-js project if that's where the error really is. Thanks!
The text was updated successfully, but these errors were encountered: