hledger/tests/query-tag.test

# 1. we parse metadata tags in transaction and posting comments. Currently,
# - they can be on the same line and/or separate lines
# - they are always printed on separate lines
hledger -f - print
<<<
2010/01/01  ; txntag1: txn val 1
  ; txntag2: txn val 2
  a             1
  ; posting1tag1: posting 1 val 1
  ; posting1tag2: 
  b            -1   ; posting-2-tag-1: posting 2 val 1
  ; posting-2-tag-2:
; non-metadata:
>>>
2010-01-01  ; txntag1: txn val 1
    ; txntag2: txn val 2
    a               1
    ; posting1tag1: posting 1 val 1
    ; posting1tag2:
    b              -1  ; posting-2-tag-1: posting 2 val 1
    ; posting-2-tag-2:

>>>2
>>>=0

# 2. reports can filter by tag existence
hledger -f - print tag:foo
<<<
2010/01/01  ; foo:bar
  a             1
  b            -1

2010/01/02  ; foo:baz
  c             1
  d            -1

2010/01/03
    e             1
    f            -1
>>>
2010-01-01  ; foo:bar
    a               1
    b              -1

2010-01-02  ; foo:baz
    c               1
    d              -1

>>>2
>>>=0

# 3. or tag value
hledger -f - print tag:foo=bar
<<<
2010/01/01  ; foo:bar
  a             1
  b            -1

2010/01/02
  ; foo:baz
  c             1
  d            -1

2010/01/03
    e             1
    f            -1
>>>
2010-01-01  ; foo:bar
    a               1
    b              -1

>>>2
>>>=0

# 4. postings inherit their transaction's tags
hledger -f - register tag:foo=bar
<<<
2010/01/01
  a             1  ; foo:bar
  b            -1

2010/01/02  ; foo:baz
  c             1
  d            -1

2010/01/03  ; foo:bar
  e             1
  f            -1
>>>
2010-01-01                      a                                1             1
2010-01-03                      e                                1             2
                                f                               -1             1
>>>2
>>>=0

# 5. look for transactions without tags
hledger -f - print not:tag:.
<<<
2010/01/01 desc
  a             1
  b            -1

2010/01/02
  ; foo:some tag
  c             2
  d            -2

2010/01/03
    e             3
    f            -3

2010/01/04 (code)
    g             4
    h            -4
>>>
2010-01-01 desc
    a               1
    b              -1

2010-01-03
    e               3
    f              -3

2010-01-04 (code)
    g               4
    h              -4

>>>=0

# 6. query is not affected by implicit tags
hledger -f ../examples/sample.journal reg tag:d
>>>
>>>2
>>>=0
more robust comments & metadata, on postings too, and document as "tags" 2012-05-14 22:52:22 +04:00			`# 1. we parse metadata tags in transaction and posting comments. Currently,`
			`# - they can be on the same line and/or separate lines`
			`# - they are always printed on separate lines`
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: parse transaction and posting metadata, though we don't use it yet 2010-11-14 01:17:32 +03:00			`<<<`
more robust comments & metadata, on postings too, and document as "tags" 2012-05-14 22:52:22 +04:00			`2010/01/01 ; txntag1: txn val 1`
			`; txntag2: txn val 2`
metadata test updates 2012-05-07 00:43:48 +04:00			`a 1`
more robust comments & metadata, on postings too, and document as "tags" 2012-05-14 22:52:22 +04:00			`; posting1tag1: posting 1 val 1`
			`; posting1tag2:`
			`b -1 ; posting-2-tag-1: posting 2 val 1`
			`; posting-2-tag-2:`
metadata test updates 2012-05-07 00:43:48 +04:00			`; non-metadata:`
parsing: parse transaction and posting metadata, though we don't use it yet 2010-11-14 01:17:32 +03:00			`>>>`
Get "make functest" (mostly) working again 2019-12-30 08:19:50 +03:00			`2010-01-01 ; txntag1: txn val 1`
more robust comments & metadata, on postings too, and document as "tags" 2012-05-14 22:52:22 +04:00			`; txntag2: txn val 2`
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`
more robust comments & metadata, on postings too, and document as "tags" 2012-05-14 22:52:22 +04:00			`; posting1tag1: posting 1 val 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			`; posting1tag2:`
;tests: normalize tests, examples, and docs using 2spcs before comments 2019-06-12 16:01:17 +03:00			`b -1 ; posting-2-tag-1: posting 2 val 1`
parse posting dates, better comment/tag handling, begin using HTF for unit testing 2012-12-06 04:28:23 +04:00			`; posting-2-tag-2:`
parsing: parse transaction and posting metadata, though we don't use it yet 2010-11-14 01:17:32 +03:00
			`>>>2`
update functional tests to shelltest 1.0 format 2011-08-15 02:15:39 +04:00			`>>>=0`
filter by metadata tag 2012-04-09 00:43:48 +04:00
new query by tag implementation 2012-05-28 04:27:55 +04:00			`# 2. reports can filter by tag existence`
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 tag:foo`
new query by tag implementation 2012-05-28 04:27:55 +04:00			`<<<`
;tests: normalize tests, examples, and docs using 2spcs before comments 2019-06-12 16:01:17 +03:00			`2010/01/01 ; foo:bar`
new query by tag implementation 2012-05-28 04:27:55 +04:00			`a 1`
			`b -1`
filter by metadata tag 2012-04-09 00:43:48 +04:00
;tests: normalize tests, examples, and docs using 2spcs before comments 2019-06-12 16:01:17 +03:00			`2010/01/02 ; foo:baz`
new query by tag implementation 2012-05-28 04:27:55 +04:00			`c 1`
			`d -1`

			`2010/01/03`
			`e 1`
			`f -1`
			`>>>`
Get "make functest" (mostly) working again 2019-12-30 08:19:50 +03:00			`2010-01-01 ; foo:bar`
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`
			`b -1`
new query by tag implementation 2012-05-28 04:27:55 +04:00
Get "make functest" (mostly) working again 2019-12-30 08:19:50 +03:00			`2010-01-02 ; foo:baz`
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			`c 1`
			`d -1`
new query by tag implementation 2012-05-28 04:27:55 +04:00
			`>>>2`
			`>>>=0`

			`# 3. or tag value`
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 tag:foo=bar`
new query by tag implementation 2012-05-28 04:27:55 +04:00			`<<<`
;tests: normalize tests, examples, and docs using 2spcs before comments 2019-06-12 16:01:17 +03:00			`2010/01/01 ; foo:bar`
new query by tag implementation 2012-05-28 04:27:55 +04:00			`a 1`
			`b -1`
metadata test updates 2012-05-07 00:43:48 +04:00
new query by tag implementation 2012-05-28 04:27:55 +04:00			`2010/01/02`
			`; foo:baz`
			`c 1`
			`d -1`
filter by metadata tag 2012-04-09 00:43:48 +04:00
new query by tag implementation 2012-05-28 04:27:55 +04:00			`2010/01/03`
			`e 1`
			`f -1`
			`>>>`
Get "make functest" (mostly) working again 2019-12-30 08:19:50 +03:00			`2010-01-01 ; foo:bar`
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`
			`b -1`
metadata test updates 2012-05-07 00:43:48 +04:00
new query by tag implementation 2012-05-28 04:27:55 +04:00			`>>>2`
			`>>>=0`
metadata test updates 2012-05-07 00:43:48 +04:00
new query by tag implementation 2012-05-28 04:27:55 +04:00			`# 4. postings inherit their transaction's tags`
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 - register tag:foo=bar`
new query by tag implementation 2012-05-28 04:27:55 +04:00			`<<<`
			`2010/01/01`
;tests: normalize tests, examples, and docs using 2spcs before comments 2019-06-12 16:01:17 +03:00			`a 1 ; foo:bar`
new query by tag implementation 2012-05-28 04:27:55 +04:00			`b -1`
metadata test updates 2012-05-07 00:43:48 +04:00
;tests: normalize tests, examples, and docs using 2spcs before comments 2019-06-12 16:01:17 +03:00			`2010/01/02 ; foo:baz`
new query by tag implementation 2012-05-28 04:27:55 +04:00			`c 1`
			`d -1`
metadata test updates 2012-05-07 00:43:48 +04:00
;tests: normalize tests, examples, and docs using 2spcs before comments 2019-06-12 16:01:17 +03:00			`2010/01/03 ; foo:bar`
new query by tag implementation 2012-05-28 04:27:55 +04:00			`e 1`
			`f -1`
			`>>>`
Get "make functest" (mostly) working again 2019-12-30 08:19:50 +03:00			`2010-01-01 a 1 1`
			`2010-01-03 e 1 2`
register: fix -w related test breakage, another width tweak (#102) As part of adding -w in december I cleaned up/adjusted register field widths, and didn't make all the tests pass. This commit makes one more width adjustment (one space after the date instead of two) and fixes all tests depending on register output. 2013-04-13 01:56:41 +04:00			`f -1 1`
new query by tag implementation 2012-05-28 04:27:55 +04:00			`>>>2`
			`>>>=0`
metadata test updates 2012-05-07 00:43:48 +04:00
Feature/pivot implicit tags (#460) * Add implicit tags code/desc/payee for --pivot Additionally allow using of transaction inherited tags. * Use original posting in query by account name To be able to query on individual postings and by account name it is useful to have access to original account name (before pivot). Especially this is useful when all postings within transaction gets the same pivot name due. As a side effect we'll match by alias. Note: to query on amt it usually expected to see matches with inferred amounts. 2017-01-13 19:02:11 +03:00			`# 5. look for transactions without tags`
			`hledger -f - print not:tag:.`
			`<<<`
			`2010/01/01 desc`
			`a 1`
			`b -1`

			`2010/01/02`
			`; foo:some tag`
			`c 2`
			`d -2`

			`2010/01/03`
			`e 3`
			`f -3`

			`2010/01/04 (code)`
			`g 4`
			`h -4`
			`>>>`
Get "make functest" (mostly) working again 2019-12-30 08:19:50 +03:00			`2010-01-01 desc`
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`
			`b -1`
Feature/pivot implicit tags (#460) * Add implicit tags code/desc/payee for --pivot Additionally allow using of transaction inherited tags. * Use original posting in query by account name To be able to query on individual postings and by account name it is useful to have access to original account name (before pivot). Especially this is useful when all postings within transaction gets the same pivot name due. As a side effect we'll match by alias. Note: to query on amt it usually expected to see matches with inferred amounts. 2017-01-13 19:02:11 +03:00
Get "make functest" (mostly) working again 2019-12-30 08:19:50 +03:00			`2010-01-03`
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			`e 3`
			`f -3`
Feature/pivot implicit tags (#460) * Add implicit tags code/desc/payee for --pivot Additionally allow using of transaction inherited tags. * Use original posting in query by account name To be able to query on individual postings and by account name it is useful to have access to original account name (before pivot). Especially this is useful when all postings within transaction gets the same pivot name due. As a side effect we'll match by alias. Note: to query on amt it usually expected to see matches with inferred amounts. 2017-01-13 19:02:11 +03:00
Get "make functest" (mostly) working again 2019-12-30 08:19:50 +03:00			`2010-01-04 (code)`
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			`g 4`
			`h -4`
Feature/pivot implicit tags (#460) * Add implicit tags code/desc/payee for --pivot Additionally allow using of transaction inherited tags. * Use original posting in query by account name To be able to query on individual postings and by account name it is useful to have access to original account name (before pivot). Especially this is useful when all postings within transaction gets the same pivot name due. As a side effect we'll match by alias. Note: to query on amt it usually expected to see matches with inferred amounts. 2017-01-13 19:02:11 +03:00
			`>>>=0`

			`# 6. query is not affected by implicit tags`
;tests: fix query-tag test 2019-07-27 08:51:15 +03:00			`hledger -f ../examples/sample.journal reg tag:d`
Feature/pivot implicit tags (#460) * Add implicit tags code/desc/payee for --pivot Additionally allow using of transaction inherited tags. * Use original posting in query by account name To be able to query on individual postings and by account name it is useful to have access to original account name (before pivot). Especially this is useful when all postings within transaction gets the same pivot name due. As a side effect we'll match by alias. Note: to query on amt it usually expected to see matches with inferred amounts. 2017-01-13 19:02:11 +03:00			`>>>`
			`>>>2`
			`>>>=0`