Bumping graphql-tag
, ignoring deprecation warnings
#1356
Merged
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.
graphql-tag
has deprecated the export of theprinter
export (which we use for various AST-related tasks here inapollo-client
). whengraphql-tag@v2
comes out, we can switch to using the printer / parser from thegraphql
package, but for now we know about the deprecation warning and can safely ignore it.addresses graphql-tag#54
TODO:
Make sure all of the significant new logic is covered by testsIf this was a change that affects the external API, update the docs and post a link to the PR in the discussion