Repository navigation
fix!: Represent prices as decimal values - #758
Open
jon-signal wants to merge 3 commits into
Open
jon-signal wants to merge 3 commits into
jon-signal wants to merge 3 commits into
Conversation
jon-signal
force-pushed
the
prices_as_big_decimal
branch
from
August 11, 2023 16:48
415acda to
ba6e519
Compare
jon-signal
force-pushed
the
prices_as_big_decimal
branch
2 times, most recently
from
August 11, 2023 17:00
3285143 to
6c75609
Compare
jon-signal
force-pushed
the
prices_as_big_decimal
branch
from
August 11, 2023 17:02
6c75609 to
e267de8
Compare
Author
|
Friends, I recognize this may not be a top priority, but is there anything I can do to help move this along to some kind of conclusion? |
tiwarishubham635
force-pushed
the
main
branch
from
September 9, 2025 08:08
6533f63 to
78a8ccd
Compare
Author
|
Hello! I wanted to check in again: is there anything I can do to help this move forward? |
Author
|
At the risk of being a nuisance, is there anything we can do to move this to a conclusion? I am happy to take "no" for an answer if that's the decision, but would love to understand next steps in any case! |
This branch has not been deployed
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.
Fixes
The Twilio API actually returns prices as strings, but the Java SDK represents them as
doublevalues. Generally, it's best to avoid floating-point representations of monetary values, and it appears that the API itself is designed with this in mind.This pull request:
doubletoBigDecimal. The existing getters are unchanged and return adoublerepresentation of the prices. I've added new getters (e.g.getBasePriceDecimal) that return the prices as lossless decimal values.The second change should be backward-compatible for most users, but I believe this is still technically a breaking change because it changes the constructors of those objects. Still, with the 10-series SDK going out, this may be a good time to make the change.
Checklist
I have added the necessary documentation about the functionality in the appropriate .md file(n/a)