- Issue created by @m.stenta
- πΊπΈUnited States m.stenta
For context, this came out of debugging this issue: π Quantity/unit price/total price auto-calculation rounding issue Fixed
Making reduce optional is one potential solution to that problem. But it also just seems like a good option to provide generally.
- @mstenta opened merge request.
- Status changed to Needs review
over 1 year ago 4:52pm 25 March 2023 - Status changed to RTBC
over 1 year ago 3:15pm 29 March 2023 - πΊπΈUnited States m.stenta
This is a simple change, and tests are passing. Setting this to RTBC.
We should tag a new minor version when this is merged since it changes the
Fraction
class API. It's backwards compatible, so I don't think we need a new major version. - Status changed to Postponed
over 1 year ago 1:00am 30 March 2023 - πΊπΈUnited States m.stenta
On second thought, I'm going to postpone this for now. It changes the API of the Fraction class, so it really should be a major version change.
And since there has been no actual demand or ask for this, I don't see any reason to prioritize a Fraction 3.x branch. When we do, we can include this.
I was originally considering it as a solution to another issue ( π Quantity/unit price/total price auto-calculation rounding issue Fixed ), but that got resolved by other means.