feat: add typename insertion functionality to graphql-tag #265
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.
Aims to close #71
Leveraging the muscle of addTypenameToDocument from the
apollo-utilities
package to add ability to add__typenames
when enabled.Parameter defined was set as
enableTypenameInsertion
anddisableTypenameInsertion
appropriatelyThe one oddity from my quick feature creation was that the
test/graphql-v0.11.js
which I didn't touch changed ever so slightly whereundefined
andnull
becamenull
and[]
I'll change it back but my
npm test
yielded the same testing compatibility fails/passes as my freshmaster
fork.Thanks for all you do! Let me know what else I can do to meet guidelines.