simonmichael/hledger
1
1
Fork 0
mirror of https://github.com/simonmichael/hledger.git synced 2025-01-06 02:23:46 +03:00
Code Issues Projects Releases Wiki Activity
660ba7e1d9
hledger/tests/journal/numbers.test

224 lines
3.0 KiB
Plaintext
Raw Normal View History

refactor: number parsing docs
2018-04-21 07:39:06 +03:00
# 1. Simple case
journal: make numbers parsing more strict - Hunt down adjacent punctuations with altering char. - Add some tests dedicated to parsing amounts.
2017-01-18 15:06:46 +03:00
hledger bal -f - --no-total
<<<
2017/1/1
a 1,000.00 EUR
b -1,000.00 EUR
>>>
1,000.00 EUR a
-1,000.00 EUR b
>>>2
>>>=0
refactor: number parsing docs
2018-04-21 07:39:06 +03:00
# 2. No digits before decimal sep
journal: make numbers parsing more strict - Hunt down adjacent punctuations with altering char. - Add some tests dedicated to parsing amounts.
2017-01-18 15:06:46 +03:00
hledger bal -f - --no-total
<<<
2017/1/1
a .01 EUR
b
>>>
0.01 EUR a
-0.01 EUR b
>>>2
>>>=0
refactor: number parsing docs
2018-04-21 07:39:06 +03:00
# 3. No digits after decimal sep
journal: make numbers parsing more strict - Hunt down adjacent punctuations with altering char. - Add some tests dedicated to parsing amounts.
2017-01-18 15:06:46 +03:00
hledger bal -f - --no-total
<<<
2017/1/1
a 1. EUR
b
>>>
1 EUR a
-1 EUR b
>>>2
>>>=0
refactor: number parsing docs
2018-04-21 07:39:06 +03:00
# 4. No digits at all
journal: make numbers parsing more strict - Hunt down adjacent punctuations with altering char. - Add some tests dedicated to parsing amounts.
2017-01-18 15:06:46 +03:00
hledger bal -f -
<<<
2017/1/1
a . EUR
b
>>>
>>>=1
refactor: number parsing docs
2018-04-21 07:39:06 +03:00
# 5. Space between digits groups
journal: support space as digits sep Resolves simonmichael/hledger#330
2017-11-02 10:36:49 +03:00
hledger bal -f - --no-total
<<<
2017/1/1
a 1 000.00 EUR
b -1 000.00 EUR
>>>
1 000.00 EUR a
-1 000.00 EUR b
>>>2
>>>=0
refactor: number parsing docs
2018-04-21 07:39:06 +03:00
# 6. Space between digits groups in commodity directive
journal: support space as digits sep Resolves simonmichael/hledger#330
2017-11-02 10:36:49 +03:00
hledger bal -f - --no-total
<<<
commodity 1 000.00 EUR
2017/1/1
a 1,000.00 EUR
b -1,000.00 EUR
>>>
1 000.00 EUR a
-1 000.00 EUR b
>>>2
>>>=0
refactor: number parsing docs
2018-04-21 07:39:06 +03:00
# 7. Default commodity
journal: use decimal sep hint for amount parser Make use of commodity format directive as a hint for parsing amount. Kinda resolves simonmichael/hledger#487
2017-10-28 18:14:54 +03:00
hledger bal -f -
<<<
D 1,000.00 EUR
2017/1/1
a 1,000
journal: get decimal hint from default commodity If appropriate commodity directive is missing fallback to default commodity directive to get number representation style.
2017-11-05 01:59:15 +03:00
b -1,000 EUR
journal: use decimal sep hint for amount parser Make use of commodity format directive as a hint for parsing amount. Kinda resolves simonmichael/hledger#487
2017-10-28 18:14:54 +03:00
>>>
1,000.00 EUR a
-1,000.00 EUR b
--------------------
0
>>>2
>>>=0
refactor: number parsing docs
2018-04-21 07:39:06 +03:00
# 8. Omitted decimals
journal: make numbers parsing more strict - Hunt down adjacent punctuations with altering char. - Add some tests dedicated to parsing amounts.
2017-01-18 15:06:46 +03:00
hledger bal -f -
<<<
2017/1/1
a 1,000 EUR
b -1,000.00 EUR
>>>
>>>=1
refactor: number parsing docs
2018-04-21 07:39:06 +03:00
# 9. Omitted decimals with commodity hint
journal: use decimal sep hint for amount parser Make use of commodity format directive as a hint for parsing amount. Kinda resolves simonmichael/hledger#487
2017-10-28 18:14:54 +03:00
hledger bal -f -
<<<
commodity 1,000.00 EUR
2017/1/1
a 1,000 EUR
b -1,000.00 EUR
>>>
1,000.00 EUR a
-1,000.00 EUR b
--------------------
0
>>>2
>>>=0
refactor: number parsing docs
2018-04-21 07:39:06 +03:00
# 10. Omitted decimals with commodity hint and symbol on left
journal: use decimal sep hint for amount parser Make use of commodity format directive as a hint for parsing amount. Kinda resolves simonmichael/hledger#487
2017-10-28 18:14:54 +03:00
hledger bal -f -
<<<
commodity €1,000.00
2017/1/1
a €1,000
b €-1,000.00
>>>
€1,000.00 a
€-1,000.00 b
--------------------
0
>>>2
>>>=0
lib: "decimal point" -> "decimal separator" in error message
2018-08-17 09:37:26 +03:00
# 11. Commodity directive requires a decimal separator
journal: use groups sep and prec for decimal hint Use whole AmountStyle in process of resolving decimal/groups separator ambiguity. Resolve simonmichael/hledger#399
2017-11-05 02:40:54 +03:00
hledger bal -f -
<<<
journal: require a decimal point in commodity/format/D directives A commodity directive that doesn't specify the decimal point character increases ambiguity and the chance of misparsing numbers, especially as it overrides all style information inferred from the journal amounts. In some cases it caused amounts with a decimal point to be parsed as if with a digit group separator so 1.234 became 1234. We could augment it with extra info from the journal amounts, when available, but it would still be possible to be ambiguous, and that won't be obvious. A commodity directive is what we recommend to nail down the style. It seems the simple and really only way to do this reliably is to require an explicit decimal point character. Most folks probably do this already. Unfortunately, it makes another potential incompatiblity with ledger and beancount journals. But the error message will be clear and easy to work around.
2018-04-21 07:56:06 +03:00
commodity 1000 EUR
;journal: fix tests
2020-03-18 03:44:32 +03:00
>>>2 /Please include a decimal point or decimal comma/
journal: require a decimal point in commodity/format/D directives A commodity directive that doesn't specify the decimal point character increases ambiguity and the chance of misparsing numbers, especially as it overrides all style information inferred from the journal amounts. In some cases it caused amounts with a decimal point to be parsed as if with a digit group separator so 1.234 became 1234. We could augment it with extra info from the journal amounts, when available, but it would still be possible to be ambiguous, and that won't be obvious. A commodity directive is what we recommend to nail down the style. It seems the simple and really only way to do this reliably is to require an explicit decimal point character. Most folks probably do this already. Unfortunately, it makes another potential incompatiblity with ledger and beancount journals. But the error message will be clear and easy to work around.
2018-04-21 07:56:06 +03:00
>>>=1
journal: use groups sep and prec for decimal hint Use whole AmountStyle in process of resolving decimal/groups separator ambiguity. Resolve simonmichael/hledger#399
2017-11-05 02:40:54 +03:00
journal: require a decimal point in commodity/format/D directives A commodity directive that doesn't specify the decimal point character increases ambiguity and the chance of misparsing numbers, especially as it overrides all style information inferred from the journal amounts. In some cases it caused amounts with a decimal point to be parsed as if with a digit group separator so 1.234 became 1234. We could augment it with extra info from the journal amounts, when available, but it would still be possible to be ambiguous, and that won't be obvious. A commodity directive is what we recommend to nail down the style. It seems the simple and really only way to do this reliably is to require an explicit decimal point character. Most folks probably do this already. Unfortunately, it makes another potential incompatiblity with ledger and beancount journals. But the error message will be clear and easy to work around.
2018-04-21 07:56:06 +03:00
# 12. Commodity directive with zero precision
journal: use groups sep and prec for decimal hint Use whole AmountStyle in process of resolving decimal/groups separator ambiguity. Resolve simonmichael/hledger#399
2017-11-05 02:40:54 +03:00
hledger bal -f -
<<<
journal: require a decimal point in commodity/format/D directives A commodity directive that doesn't specify the decimal point character increases ambiguity and the chance of misparsing numbers, especially as it overrides all style information inferred from the journal amounts. In some cases it caused amounts with a decimal point to be parsed as if with a digit group separator so 1.234 became 1234. We could augment it with extra info from the journal amounts, when available, but it would still be possible to be ambiguous, and that won't be obvious. A commodity directive is what we recommend to nail down the style. It seems the simple and really only way to do this reliably is to require an explicit decimal point character. Most folks probably do this already. Unfortunately, it makes another potential incompatiblity with ledger and beancount journals. But the error message will be clear and easy to work around.
2018-04-21 07:56:06 +03:00
commodity 100. EUR
journal: use groups sep and prec for decimal hint Use whole AmountStyle in process of resolving decimal/groups separator ambiguity. Resolve simonmichael/hledger#399
2017-11-05 02:40:54 +03:00
2017/1/1
a 1,000 EUR
b -1,000.00 EUR
>>>
1000 EUR a
-1000 EUR b
--------------------
0
>>>2
>>>=0
refactor: number parsing docs
2018-04-21 07:39:06 +03:00
# 13. Big prices
journal: make numbers parsing more strict - Hunt down adjacent punctuations with altering char. - Add some tests dedicated to parsing amounts.
2017-01-18 15:06:46 +03:00
hledger bal -f - --no-total
<<<
2017/1/1
a -1 BTC @ 24,840 UAH
b 24,840.00 UAH
>>>
>>>=1
refactor: number parsing docs
2018-04-21 07:39:06 +03:00
# 14. Big prices with commodity hint
journal: use decimal sep hint for amount parser Make use of commodity format directive as a hint for parsing amount. Kinda resolves simonmichael/hledger#487
2017-10-28 18:14:54 +03:00
hledger bal -f - --no-total
<<<
commodity ₴1,000.00
2017/1/1
a -1 BTC @ ₴24,840
b ₴24,840.00
>>>
-1 BTC a
₴24,840.00 b
>>>2
>>>=0
refactor: number parsing docs
2018-04-21 07:39:06 +03:00
# 15. adjacent punctuation chars
journal: make numbers parsing more strict - Hunt down adjacent punctuations with altering char. - Add some tests dedicated to parsing amounts.
2017-01-18 15:06:46 +03:00
hledger bal -f -
<<<
2017/1/1
a 1,,0,,0.0 EUR
b -1..0..0,0 EUR
>>>
>>>=1
refactor: number parsing docs
2018-04-21 07:39:06 +03:00
# 16. adjacent punctuation chars of different types
journal: make numbers parsing more strict - Hunt down adjacent punctuations with altering char. - Add some tests dedicated to parsing amounts.
2017-01-18 15:06:46 +03:00
hledger bal -f -
<<<
2017/1/1
a 1,0,.0 EUR
b -1.0.,0 EUR
>>>
>>>=1
refactor: number parsing docs
2018-04-21 07:39:06 +03:00
# 17. separator chars vary
journal: make numbers parsing more strict - Hunt down adjacent punctuations with altering char. - Add some tests dedicated to parsing amounts.
2017-01-18 15:06:46 +03:00
hledger bal -f -
<<<
2017/1/1
a 1.0,0.0,0 EUR
b -1,0.0,0.0 EUR
>>>
>>>=1
refactor: number parsing docs
2018-04-21 07:39:06 +03:00
# 18. number begins with a decimal char
journal: make numbers parsing more strict - Hunt down adjacent punctuations with altering char. - Add some tests dedicated to parsing amounts.
2017-01-18 15:06:46 +03:00
hledger bal -f -
<<<
2017/1/1
a .1 EUR
b -.1 EUR
>>>
0.1 EUR a
-0.1 EUR b
--------------------
0
>>>2
>>>=0
refactor: number parsing docs
2018-04-21 07:39:06 +03:00
# 19. number begins with a separator char
journal: make numbers parsing more strict - Hunt down adjacent punctuations with altering char. - Add some tests dedicated to parsing amounts.
2017-01-18 15:06:46 +03:00
hledger bal -f -
<<<
2017/1/1
a ,100.0 EUR
b -,100.0 EUR
>>>
>>>=1
Reference in New Issue Copy Permalink