This repository has been archived by the owner on Apr 14, 2023. It is now read-only.
Use print from graphql directly instead of from graphql-tag #98
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.
TODO:
What's up?
Hey! While updating
meteor/apollo
to use this package (yay! 🚀), we encountered the warning about deprecation ofprint
fromgraphql-tag
(apollographql/meteor-integration#87).Following discussions from apollographql/graphql-tag#54 & others PRs/issues related, I've made the change & I've tried it locally: tests pass and it works.
I assumed that
graphql
should be then independencies
more thandevDependencies
, right?