hledger/tests/journal/dates.test

# invalid dates should be rejected
# 1. valid month and day, but flipped
hledger -f- print
<<<
2010/31/12 x
   a  1
   b
>>>2 /invalid date/
>>>= 1
# 2. too-large day
hledger -f- print
<<<
2010/12/32 x
   a  1
   b
>>>2 /invalid date/
>>>= 1
# 3. 29th feb on leap year should be ok
hledger -f- print
<<<
2000/2/29 x
   a  1
   b
>>>
2000-02-29 x
    a               1
    b

>>>= 0
# 4. 29th feb on non-leap year should fail
hledger -f- print
<<<
2001/2/29 x
   a  1
   b
>>>2 /invalid date/
>>>= 1
# 5. dates must be followed by whitespace or newline
hledger -f- print
<<<
2015/9/6*
   a  0
>>>2 /unexpected '*'/
>>>= 1
update leap year tests 2011-04-20 01:40:59 +04:00			`# invalid dates should be rejected`
			`# 1. valid month and day, but flipped`
tests: make functional tests use "hledger" again Using "hledgerdev" was a hack to help ensure that tests used a fresh developer build by default. Now they specify "hledger" again, which fits better with stack. It's up to the tester to make sure the desired executable is first in PATH or specified with -w. (Note a couple of tests currently don't obey -w and will always run "hledger", see addons.test). 2015-07-12 21:54:08 +03:00			`hledger -f- print`
parsing: show a better error for illegal month/day numbers in dates 2010-04-06 06:31:47 +04:00			`<<<`
			`2010/31/12 x`
			`a 1`
			`b`
lib: refactor date parser 2018-05-23 05:17:51 +03:00			`>>>2 /invalid date/`
parsing: show a better error for illegal month/day numbers in dates 2010-04-06 06:31:47 +04:00			`>>>= 1`
update leap year tests 2011-04-20 01:40:59 +04:00			`# 2. too-large day`
tests: make functional tests use "hledger" again Using "hledgerdev" was a hack to help ensure that tests used a fresh developer build by default. Now they specify "hledger" again, which fits better with stack. It's up to the tester to make sure the desired executable is first in PATH or specified with -w. (Note a couple of tests currently don't obey -w and will always run "hledger", see addons.test). 2015-07-12 21:54:08 +03:00			`hledger -f- print`
parsing: show a better error for illegal month/day numbers in dates 2010-04-06 06:31:47 +04:00			`<<<`
			`2010/12/32 x`
			`a 1`
			`b`
lib: refactor date parser 2018-05-23 05:17:51 +03:00			`>>>2 /invalid date/`
parsing: show a better error for illegal month/day numbers in dates 2010-04-06 06:31:47 +04:00			`>>>= 1`
update leap year tests 2011-04-20 01:40:59 +04:00			`# 3. 29th feb on leap year should be ok`
tests: make functional tests use "hledger" again Using "hledgerdev" was a hack to help ensure that tests used a fresh developer build by default. Now they specify "hledger" again, which fits better with stack. It's up to the tester to make sure the desired executable is first in PATH or specified with -w. (Note a couple of tests currently don't obey -w and will always run "hledger", see addons.test). 2015-07-12 21:54:08 +03:00			`hledger -f- print`
tests: 29th feb should be correctly handled wrt leap/non-leap year 2011-04-20 00:15:14 +04:00			`<<<`
update leap year tests 2011-04-20 01:40:59 +04:00			`2000/2/29 x`
tests: 29th feb should be correctly handled wrt leap/non-leap year 2011-04-20 00:15:14 +04:00			`a 1`
			`b`
			`>>>`
Get "make functest" (mostly) working again 2019-12-30 08:19:50 +03:00			`2000-02-29 x`
lib: keep amounts aligned when rendering a transaction with posting flags Related to #563, when rendering a transaction, we reserve two more chars of width so that amounts remain aligned when there are posting flags. Affects hledger-ui's transaction screen, print, hledger-rewrite etc. 2017-06-05 07:26:18 +03:00			`a 1`
Preserve implicit amounts and prices the way user wrote them in output of print command (#471) * Remember original postings during infer and pivot This includes such functions like: - inferFromAssignment - inferBalancingAmount - inferBalancingPrices - pivotPosting * Use original postings for hledger print - Introduce "--explicit" option for "print" command which brings back old behavior when every inferred number being printed. - Make "print" by default print original postings without inferred amounts. But use effective account name to have effect from aliases. - Instruct shell tests with an new expected output or to use --explicit option when inferred amounts are checked. Resolves simonmichael/hledger#442 2017-01-13 18:25:44 +03:00			`b`
update leap year tests 2011-04-20 01:40:59 +04:00
tests: 29th feb should be correctly handled wrt leap/non-leap year 2011-04-20 00:15:14 +04:00			`>>>= 0`
parsing: more careful validation of eg leap years in transaction dates (only) 2011-04-22 17:55:42 +04:00			`# 4. 29th feb on non-leap year should fail`
tests: make functional tests use "hledger" again Using "hledgerdev" was a hack to help ensure that tests used a fresh developer build by default. Now they specify "hledger" again, which fits better with stack. It's up to the tester to make sure the desired executable is first in PATH or specified with -w. (Note a couple of tests currently don't obey -w and will always run "hledger", see addons.test). 2015-07-12 21:54:08 +03:00			`hledger -f- print`
tests: 29th feb should be correctly handled wrt leap/non-leap year 2011-04-20 00:15:14 +04:00			`<<<`
update leap year tests 2011-04-20 01:40:59 +04:00			`2001/2/29 x`
tests: 29th feb should be correctly handled wrt leap/non-leap year 2011-04-20 00:15:14 +04:00			`a 1`
			`b`
lib: refactor date parser 2018-05-23 05:17:51 +03:00			`>>>2 /invalid date/`
tests: 29th feb should be correctly handled wrt leap/non-leap year 2011-04-20 00:15:14 +04:00			`>>>= 1`
lib: fix bracketed posting dates, parser cleanup (#304) Bracketed posting dates were fragile; they worked only if you wrote full 10-character dates. Also some semantics were a bit unclear. Now they should be robust, and have been documented more clearly. This is a legacy undocumented Ledger syntax, but it improves compatibility and might be preferable to the more verbose "date:" tags if you write posting dates often (as I do). Internally, bracketed posting dates are no longer considered to be tags. Journal comment, tag, and posting date parsers have been reworked, all with doctests. Also the journal parser types generally have been tightened up and clarified, making it much easier to know how to combine and run them. There's now -- \| A parser of strings with generic user state, monad and return type. type StringParser u m a = ParsecT String u m a -- \| A string parser with journal-parsing state. type JournalParser m a = StringParser JournalContext m a -- \| A journal parser that runs in IO and can throw an error mid-parse. type ErroringJournalParser a = JournalParser (ExceptT String IO) a and corresponding convenience functions (and short aliases) for running them. 2016-04-28 23:23:20 +03:00			`# 5. dates must be followed by whitespace or newline`
tests: make functional tests use "hledger" again Using "hledgerdev" was a hack to help ensure that tests used a fresh developer build by default. Now they specify "hledger" again, which fits better with stack. It's up to the tester to make sure the desired executable is first in PATH or specified with -w. (Note a couple of tests currently don't obey -w and will always run "hledger", see addons.test). 2015-07-12 21:54:08 +03:00			`hledger -f- print`
journal: dates should be followed by whitespace or newline 2014-09-06 20:20:22 +04:00			`<<<`
lib: fix bracketed posting dates, parser cleanup (#304) Bracketed posting dates were fragile; they worked only if you wrote full 10-character dates. Also some semantics were a bit unclear. Now they should be robust, and have been documented more clearly. This is a legacy undocumented Ledger syntax, but it improves compatibility and might be preferable to the more verbose "date:" tags if you write posting dates often (as I do). Internally, bracketed posting dates are no longer considered to be tags. Journal comment, tag, and posting date parsers have been reworked, all with doctests. Also the journal parser types generally have been tightened up and clarified, making it much easier to know how to combine and run them. There's now -- \| A parser of strings with generic user state, monad and return type. type StringParser u m a = ParsecT String u m a -- \| A string parser with journal-parsing state. type JournalParser m a = StringParser JournalContext m a -- \| A journal parser that runs in IO and can throw an error mid-parse. type ErroringJournalParser a = JournalParser (ExceptT String IO) a and corresponding convenience functions (and short aliases) for running them. 2016-04-28 23:23:20 +03:00			`2015/9/6*`
journal: dates should be followed by whitespace or newline 2014-09-06 20:20:22 +04:00			`a 0`
Replace Parsec with Megaparsec (see #289) (#366) * Replace Parsec with Megaparsec (see #289) This builds upon PR #289 by @rasendubi * Revert renaming of parseWithState to parseWithCtx * Fix doctests * Update for Megaparsec 5 * Specialize parser to improve performance * Pretty print errors * Swap StateT and ParsecT This is necessary to get the correct backtracking behavior, i.e. discard state changes if the parsing fails. 2016-07-29 18:57:10 +03:00			`>>>2 /unexpected '*'/`
journal: dates should be followed by whitespace or newline 2014-09-06 20:20:22 +04:00			`>>>= 1`