Add new GraphQLJson type to the CustomTypeValue #897
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Current implementation allows Map to be serialized as JSON string value, with this changes we introduce new CustomTypeValue type that will allow Map to be serialized as regular JSON object. Closes apollographql#873
sav007
force-pushed
the
feature-873/json-as-input
branch
from
74b6ed6 to
ca2a184
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Current implementation allows Map to be serialized as JSON string value, with this changes we introduce new CustomTypeValue type that will
allow Map to be serialized as regular JSON object.
Closes #873