Use getIntrospectionQuery
rather than introspectionQuery
constant.
#5748
+2
−2
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.
The next major version of
graphql-js
deprecates theintrospectionQuery
constant (thanks to graphql/graphql-js#2124) that was previously leveraged in Apollo Client tests for obtaining the introspection query (to be clear, this is the query used to introspect a server, not the result of the introspection itself) in one particular test.This deprecation isn't entirely surprising since the
getIntrospectionQuery
utility method has existed since[email protected]
and is the recommended way to obtain this query in more recent versions ofgraphql
, so this changes that test to use that new method.I discovered this while investigating our compatibility with the most recently published
[email protected]
onapollo-server
,apollo-tooling
andapollo-client
. Other than this, I didn't encounter any test failures when updating the rootgraphql
dev-dependency to[email protected]
!Deprecated by: graphql/graphql-js#2124
In Response to: graphql/graphql-js#2303
Relates to: apollographql/apollo-server#3649
Relates to: apollographql/apollo-tooling#1743