hledger/tests/misc
Simon Michael 8d75635505 print: limit display precision of generated prices (#262)
When a transaction posts to two commodities without specifying the
conversion price, we generate a price which makes it balance
(cf http://hledger.org/manual.html#prices).

Until now, these generated prices were always shown with full precision
(all available decimal digits) so that a manual calculation with the
displayed numbers would agree.

If there's just one posting in the commodity being priced, we can use an
exact total price and the precision is no problem.

But if there are multiple postings in the commodity being priced, we
must show the averaged unit price. This can be an irrational number,
which with our current Decimal-based implementation would display an
excessive 255 decimal digits. So in this case we now set the price's
display precision to the sum of the (max) display precisions of the
commodities involved. An example:

hledgerdev -f- print
<<<
1/1
    c    C 10.00
    c    C 11.00
    d  D -320.00
>>>
2015/01/01
    c  C 10.00 @ D 15.2381
    c  C 11.00 @ D 15.2381
    d     D -320.00

>>>=0

There might still be cases where this will show more price decimal
places than necessary. For now, YAGNI.
2015-05-27 14:21:19 -07:00
..
aliases.test journal: re-add non-regex aliases, as default (#252) 2015-05-14 13:01:50 -07:00
amount-rendering.test register: optimise postingsReportItemAsText a bit 2014-07-07 08:37:27 -07:00
commodities.test reorganise functional tests by command/topic 2014-05-06 21:02:58 -07:00
precision.test print: limit display precision of generated prices (#262) 2015-05-27 14:21:19 -07:00
prices.test reorganise functional tests by command/topic 2014-05-06 21:02:58 -07:00
query-status.test fix func. test numbering 2014-09-13 21:28:07 -07:00
tags.test reorganise functional tests by command/topic 2014-05-06 21:02:58 -07:00
virtual-postings.test reorganise functional tests by command/topic 2014-05-06 21:02:58 -07:00