Update test fixtures to use string descriptions where tested #153
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
👋 I saw that some tests were skipped on GraphQL-Ruby v2.2+, so I took a look into it.
It looks like the new Ruby parser broke it. The old parser supported comments-as-descriptions, but the new parser doesn't. So these tests for descriptions started failing.
I updated these example to use strings instead of comments so that the tests would keep passing. (Strings have been the only "official" format for descriptions since 2018 or so: graphql/graphql-spec#420.)
To update the whole example, we could probably use GraphQL-Ruby 2.1.x do something like
GraphQL::Schema.from_definition(...).to_definition
to generate a new, spec-compliant schema definition file.What do you think of this approach? Would it be helpful to update all the fixtures to the current format?