allow null as well as '{}' for empty objects in json#62
Open
kryton wants to merge 1 commit intoEOSIO:masterfrom
Open
allow null as well as '{}' for empty objects in json#62kryton wants to merge 1 commit intoEOSIO:masterfrom
kryton wants to merge 1 commit intoEOSIO:masterfrom
Conversation
Author
|
NB:.. serde_json still won't fully work with variants. |
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
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.
certain json parsers (serde_json in rust) convert no-field empty structs as null, instead of '{}'.
This patch allows for both ways to seen as valid.
(for example)
["get_status_request_v0",null]
as well as
["get_status_request_v0",{}]