Changes to support raw json fields #41
Open
Conversation
This file contains 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
By specifing json.RawMessage as a field type in a query raw json fields can be queried and returned.
Fix `go vet` call to work with newer go toolchains.
|
Is this going in any time soon? |
|
I would be in favor of that but its not my call ;) |
rideliner
added a commit
to arvata-io/graphql
that referenced
this pull request
May 18, 2020
alexandear
pushed a commit
to alexandear/graphql
that referenced
this pull request
Jan 8, 2024
* Propagate errors instead of panic
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.
By specifing json.RawMessage as a field type in a query raw
json fields can be queried and returned.
This would address #32