Recommendations on limiting rendered tolerances/precisions

[coltonc...@gmail.com]

I populated price data with bean-price which is causing fava to show a lot of decimal places (~14).

This happens regardless if the price data is in my main beancount file or a secondary one.

I read through everything I could find but what I've gathered is that tolerances and precisions are inferred first and foremost (before considering any options). Is there a recommendation here? Is the only path forward to modify all the price data to only have two decimal places? I've been looking mostly in these place:

- https://docs.google.com/document/d/1lgHxUUEY-UVEgoF6cupz2f_7v7vEF7fiJyiSlYYlhOo/edit#

- https://groups.google.com/g/beancount/c/tsYAf02DSq4/m/ZaQrFQ0xAgAJ

- https://github.com/beancount/beancount/blob/master/beancount/parser/options.py

Colton

[William Bean]

Was wondering the same thing. Does anyone have any insights? If not, is there more user control over decimal places intended in v3?

[Josh D]

I looked this up recently. It's in fava's help section. The following defines the "number of decimal places" to show in Fava. It's user adjustable.

[Commodities]
Declaring commodities is optional. Use this if you want to attach metadata by currency. If you specify a name for a currency like below, this name will be displayed as a tooltip on hovering over currency names in Fava. Likewise, with the precision metadata, you can specify the number of decimal digits to show in Fava, overriding the precision that is otherwise automatically inferred from the input data.

1998-07-22 commodity AAPL
name: "Apple Computer Inc."
precision: 3

[William Bean]

Great find, Josh! Looks like that was incorporated at some point last year, so I didn't realize it was a feature. Thanks for sharing.