Add json input and output support #19
Merged
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
needs review.. code may now be GNU only
this preserves the ordering of fields while enabling binary search. required for the new parse function so authors have control over loading field dependencies.
not needed with all field types now supported
don't use get functions
this makes the json output more usable even though it adds nothing for json deserialization
rather than emitting null and empty arrays we skip fields with no entries entirely
cmikk
added a commit
that referenced
this pull request
Oct 2, 2015
Add json input and output support
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.
This adds several features to nmsg. Message modules now have a format and parse function for fields. Support for this should be added to pynmsg.
You can output messages in json format with the -J option to nmsgtool. You can input messages in json format with the -j option. JSON blobs with parse errors are ignored (and reported with debug >= 1).
This is blocked on lloyd/yajl#168 being accepted, unless you don't mind memory leakage on parse errors (or you merge my commits into your own build).