use BigDecimal for currency amounts and remove '_cents' suffix about cobudget-api HOT 5 CLOSED

I'd like to not even have cents in the whole process and just stick to dollars. And then only switch to using cents once we start doing multiple currencies...

from cobudget-api.

i don't have an opinion on whether the user experience should be in dollars or cents or whatever, i do think that either way we should use BigDecimal on the backend so we have the technical flexibility of infinite precision numbers without rounding errors.

from cobudget-api.

But if we're not using cents then wouldn't it make more sense to not store decimals at all?

On Mon, Dec 8, 2014 at 3:14 PM, Michael Williams [email protected]
wrote:

i don't have an opinion on whether the user experience should include dollars or cents or whatever, i think we should use BigDecimal regardless so we have the technical flexibility of infinite precision without rounding errors.

Reply to this email directly or view it on GitHub:
#34 (comment)

from cobudget-api.

decimals provide flexibility, they can do everything integers can do and more, so we can do whatever we want with our numbers and it'll be supported without additional rewrites. i have a hard time believing we will never ever want to use cents or other fractional amounts, so why not plan this current rewrite for something that works for all cases so we don't have to rewrite this code again when the user stories change. also integers have a max value, not that i think we'd hit the max with our current orgs.

from cobudget-api.

bump

from cobudget-api.