-
-
Notifications
You must be signed in to change notification settings - Fork 35
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
feat: add very large amount support #91
base: master
Are you sure you want to change the base?
feat: add very large amount support #91
Conversation
nesquikm
commented
Feb 18, 2025
- Updated Money JSON serialization format
- Simplified Money formatting with default pattern
- Improved currency precision calculation
- Added tests for large scale and integer handling
- Enhanced pattern encoding and formatting flexibility
…ber handling - Updated Money JSON serialization format - Simplified Money formatting with default pattern - Improved currency precision calculation - Added tests for large scale and integer handling - Enhanced pattern encoding and formatting flexibility
… scales and integers
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so the json changes look to be breaking.
Not necessarily a problem but is this an improvement for end users?
This is improvement for architecture. What the point having from/to json in Fixed (that works perfectly) and parsing it here as string? |
I'm not certain I would call this an architectural issue given it's one
function. It's not exactly going to cause us a maintenance issue.
I also always argue in favour of making the users life easier over ours.
This change doesn't make our life easier (the existing code works and will
require no further maintenance) whilst the change will break user code in
places that are hard to fix for them.
E.g. if they are storing the json in a db, fixing the db to accommodate
this change will be a major pain and one likely to cause runtime errors in
production of they miss something.
…On Sat, 22 Feb 2025, 7:20 pm Mike, ***@***.***> wrote:
so the json changes look to be breaking. Not necessarily a problem but is
this an improvement for end users?
This is improvement for architecture. What the point having from/to json
in Fixed (that works perfectly) and parsing it here as string?
—
Reply to this email directly, view it on GitHub
<#91 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAG32OE5KJ5CMCIO4S4MOYT2RAXLXAVCNFSM6AAAAABXLT4QMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZWGA4DONBWGE>
.
You are receiving this because you commented.Message ID: <onepub-dev/money
.***@***.***>
[image: nesquikm]*nesquikm* left a comment (onepub-dev/money.dart#91)
<#91 (comment)>
so the json changes look to be breaking. Not necessarily a problem but is
this an improvement for end users?
This is improvement for architecture. What the point having from/to json
in Fixed (that works perfectly) and parsing it here as string?
—
Reply to this email directly, view it on GitHub
<#91 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAG32OE5KJ5CMCIO4S4MOYT2RAXLXAVCNFSM6AAAAABXLT4QMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZWGA4DONBWGE>
.
You are receiving this because you commented.Message ID: <onepub-dev/money
.***@***.***>
|
We can wrap |
That is certainly better but still leaves users with having to upgrade
client/ server systems simultaneously - or at least the reader needs to be
updated first.
It is also a problem if they are using any third party tools to read the
json as they will now have two forms of the json in their db.
I'm still struggling to see a benefit of this change that out ways the cost
to users.
…On Tue, 25 Feb 2025, 2:22 am Mike, ***@***.***> wrote:
We can wrap Fixed.fromJson(...) in try...catch and, if it fails, call
Fixed.parse(...). This will provide seamless migration from existing
(stored somewhere) records. What do you think?
—
Reply to this email directly, view it on GitHub
<#91 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAG32ODSBAJCK7HM4UJX2DT2RM2LRAVCNFSM6AAAAABXLT4QMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZYG44DCNZRGA>
.
You are receiving this because you commented.Message ID: <onepub-dev/money
.***@***.***>
[image: nesquikm]*nesquikm* left a comment (onepub-dev/money.dart#91)
<#91 (comment)>
We can wrap Fixed.fromJson(...) in try...catch and, if it fails, call
Fixed.parse(...). This will provide seamless migration from existing
(stored somewhere) records. What do you think?
—
Reply to this email directly, view it on GitHub
<#91 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAG32ODSBAJCK7HM4UJX2DT2RM2LRAVCNFSM6AAAAABXLT4QMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZYG44DCNZRGA>
.
You are receiving this because you commented.Message ID: <onepub-dev/money
.***@***.***>
|