Use BigDecimal instead of Double to avoid loss of precision #42
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.
In our use case, the loss of precision when parsing decimal numbers as floating point is not acceptable. This pull request proposes switching parsing from
Double
toBigDecimal
. Because this is a behaviour change, it puts it behind thejettison.json.jsontokener.use_bigdecimal
system property so that other consumers are unaffected unless they opt in.