This repository was archived by the owner on Dec 24, 2022. It is now read-only.
Added JsConfig option to propagate serialization exceptions up the stack rather than swallowing - #86
Merged
Conversation
…ere not outputing correctly formed JSON and were ommiting the word null
mythz
added a commit
that referenced
this pull request
Mar 11, 2012
Added JsConfig option to propagate serialization exceptions up the stack rather than swallowing
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
I added a JsConfig option to propagate serialization exceptions up the stack rather than swallowing them. This is valuable for financial applications and other types of applications where the accuracy of every field matters. Also added unit tests.