Add new json input type that should be used for service properties #317
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.
Changelog
changie
entryTophatting
See the test assertions in
TestNewJSON
to show how it takes in different types like, bool, number, array and maps and property marshals them to string data that will get passed to our API. We could just use astring
and force the customer to usejson.Marshal
themselves but we don't for 3 reasonsJsonString
in the mutation - see theTestConstructQueryJSON
andTestConstructMutationJSON