Skip to content

Use getIntrospectionQuery instead of deprecated introspectionQuery constant #1228

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

Merged
merged 1 commit into from
Oct 24, 2019
Merged

Use getIntrospectionQuery instead of deprecated introspectionQuery constant #1228

merged 1 commit into from
Oct 24, 2019

Conversation

derek-miller
Copy link
Contributor

@derek-miller derek-miller commented Oct 23, 2019

introspectionQuery is being removed in v15 of graphql-js.

@apollo-cla
Copy link

@derek-miller: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Apollo Contributor License Agreement here: https://contribute.apollographql.com/

Copy link
Contributor

@benjamn benjamn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @derek-miller!

@@ -1,10 +1,11 @@
import { GraphQLSchema, DocumentNode } from 'graphql';
import { introspectionQuery, buildClientSchema, parse } from 'graphql';
import { buildClientSchema, parse } from 'graphql';
import { getIntrospectionQuery } from 'graphql/utilities';
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need to change this before merging this PR, but we could make these imports more specific:

import { parse } from 'graphql/language/parser';
import { buildClientSchema } from 'graphql/utilities/buildClientSchema';
import { getIntrospectionQuery } from 'graphql/utilities/introspectionQuery';

That said, what you've done is already an improvement over importing from 'graphql'.

@benjamn benjamn merged commit a49e9e2 into ardatan:master Oct 24, 2019
@benjamn
Copy link
Contributor

benjamn commented Oct 24, 2019

Quick note: it looks like we will need to fix the failing tests on master before releasing this change. I (or possibly @hwillson) can look into that tomorrow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants