Skip to content

graphiql version upgrade close #572 #639

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
May 15, 2019
Merged

Conversation

Zorig
Copy link
Contributor

@Zorig Zorig commented May 15, 2019

No description provided.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 92.712% when pulling ba64bce on Zorig:master into e26a9f2 on graphql-python:master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage remained the same at 92.712% when pulling ba64bce on Zorig:master into e26a9f2 on graphql-python:master.

@phalt
Copy link
Contributor

phalt commented May 15, 2019

@Zorig have you tested that this works? We don't need to do anything else?

@Zorig
Copy link
Contributor Author

Zorig commented May 15, 2019

@phalt i think so, the template file is getting graphiql version from view then fetch from CDN.

@phalt
Copy link
Contributor

phalt commented May 15, 2019

@Zorig if you've tested it locally then I'll go ahead and merge it :)

@Zorig
Copy link
Contributor Author

Zorig commented May 15, 2019

yup, go ahead.

@phalt phalt merged commit 96908be into graphql-python:master May 15, 2019
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