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

;doc:csv: How CSV rules are evaluated: clarify

Browse Source
This commit is contained in:
Simon Michael 2025-04-16 16:29:53 -10:00
parent 15218a3d56
commit 5c3197dd42
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
hledger/hledger.m4.md
View File

@ -4255,7 +4255,8 @@ If you get a confusing error while reading a CSV file, it may help to try to und
1. Any [included](#include) rules files are inlined, from top to bottom, depth first 1. Any [included](#include) rules files are inlined, from top to bottom, depth first
(scanning each included file for further includes, recursively, before proceeding). (scanning each included file for further includes, recursively, before proceeding).
2. Top level rules (`date-format`, `fields`, `newest-first`, `skip` at top level, etc) are processed, top to bottom. 2. Top level rules (`date-format`, `fields`, `newest-first`, `skip` at top level, etc)
are read, top to bottom.
If a rule occurs more than once, the last one wins; If a rule occurs more than once, the last one wins;
except for `skip`/`end` rules, where the first one wins. except for `skip`/`end` rules, where the first one wins.