Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix problem with precision when retrieving BigDecimal JSON properties. #482

Closed
wants to merge 1 commit into from
Closed

Conversation

sollecitom
Copy link

As it is now, retrieving a property with value "0.01" with JSONObject.getBigDecimal(key) will return "0.01000000000000000020816681711721685132943093776702880859375" instead "0.01".

As it is now, retrieving a property with value "0.01" with `JSONObject.getBigDecimal(key)` will return "0.01000000000000000020816681711721685132943093776702880859375" instead "0.01".
@stleary
Copy link
Owner

stleary commented Sep 6, 2019

Breaks unit tests. Please see https://github.com/stleary/JSON-Java-unit-test

@stleary
Copy link
Owner

stleary commented Sep 6, 2019

@sollecitom Thanks for the pull request, it is appreciated. This project is in maintenance mode, so most changes are user-driven. We ask that code submitters follow the process from end to end, which includes ensuring the unit tests pass, as described in this wiki page: https://github.com/stleary/JSON-java/wiki/How-to-contribute-code-for-this-project

Breakages may indicate a change in behavior to existing code. When that happens, we have to determine if fixing the problem is more urgent than potentially breaking existing applications. You can find more information about this in the FAQ.

@johnjaylward
Copy link
Contributor

Also, see PR #453 and issue #441 which also address issues similar to this one

@stleary
Copy link
Owner

stleary commented Oct 8, 2019

Closed for inactivity.

@stleary stleary closed this Oct 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants