A lot of decimal digits if using total price

[blais]

Original report by Jakob Schnitzer (Bitbucket: yagebu, GitHub: yagebu).

---

The bean-web journal (and the fava journal) use the input precision to render units, price and cost. I actually like this as it allows me to spot problems with the data in my file. However, some computed will be shown with ~20 decimal digits.

I've input most of my transactions in foreign currencies using a total price with @@, e.g. 9.50 GBP @@ 11.18 EUR. This leads to a price with a lot of unnecessary digits (1.176842105263157894736842105 EUR in the example), as the number don't divide nicely. It would be nice if beancount would only calculate the price number of digits required to make the transaction balance under the known tolerances. Or is there some reason why this behaviour would be bad?

[blais]

Original comment by Martin Blais (Bitbucket: blais, GitHub: blais).

---

This is an interesting idea I hadn't thought about, basically for the completion to round from the most precise until the tolerance fails. I like this. Will definitely consider this and implement eventually.