Add Operation.Data.toJsonString() convenience function for the jvm #4124
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.
Allows a more convenient way to simply get the Json representation from
Operation.Data
without having to manually deal with Buffers etc in client code which the currenttoJson
function requires.This could be imitated on the clients by instead calling the existing
toJson
function like this:Which should be functionally equivalent to what the introduced function does (if we inlined
buildJsonString
whichtoJsonString
uses internally)If you believe that the API doesn't need this addition that would be totally understandable, and you can feel free to simply close this PR 🙌