slaesvuo/hledger
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

;doc: assertions and multiple files: edits

Browse Source
This commit is contained in:
Simon Michael 2025-04-25 18:25:12 -10:00
parent 3b4ab7d659
commit dca05e2542
1 changed files with 6 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
hledger/hledger.m4.md
View File

@ -1685,23 +1685,22 @@ If the same files are siblings, the assertions will not work.
For example if you specify them with two `-f` options on the command line, For example if you specify them with two `-f` options on the command line,
the assertions in one will not see the balances from the other. the assertions in one will not see the balances from the other.
But also, if a parent file includes the two subfiles with two side-by-side `include` directives, But also, if a parent file includes the two subfiles with two side-by-side `include` directives, this too will fail (I think I have that right).
this too will fail (I think I have that right).
Assertions in one subfile will not see the balances from the other. Assertions in one subfile will not see the balances from the other.
To work around this, arrange your files in parent child relationships with `include`. To work around this, arrange your files in parent child relationships with `include`.
Eg make one subfile `include`` the other (it doesn't matter which way round). Eg make one subfile include the other (it doesn't matter which way round).
Or, you could concatenate the files temporarily, and process them like one big file. Or, you could concatenate the files temporarily, and process them like one big file. Eg:\
Eg, `hledger print -I | hledger -f- CMD` `hledger print -I | hledger -f- CMD`
Why does it work this way ? Why does it work this way ?
IIRC it might be related to hledger's goal of stable predictable reports. It might be related to hledger's goal of stable predictable reports.
File hierarchy is considered "permanent" - it's part of your data. File hierarchy is considered "permanent" - it's part of your data.
Whereas the order of sibling files (on the command line at least) is transient - it can change from one command to the next. Whereas the order of sibling files (on the command line at least) is transient - it can change from one command to the next.
We don't want transient changes to be able to change the meaning of the data. We don't want transient changes to be able to change the meaning of the data.
Eg it would be frustrating if tomorrow all your balance assertions broke because you wrote command line arguments in a different order. Eg it would be frustrating if tomorrow all your balance assertions broke because you wrote command line arguments in a different order.
Feel free to discuss this more. (Discussion welcome.)
### Assertions and costs ### Assertions and costs