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

;doc: csv: try to clarify how CSV fields and hledger fields work

Browse Source
This commit is contained in:
Simon Michael 2023-01-19 05:58:16 -10:00
parent 1c9a44cae9
commit b4501a270d
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
hledger/hledger.m4.md
View File

@ -3076,10 +3076,10 @@ Note the two kinds of "field names" used in hledger CSV rules:
2. **hledger field names** (`HLEDGERFIELD` in examples):\
These are special reserved names corresponding (directly or indirectly) to parts of a hledger transaction.
If you use one of these names in a [`fields` list](#fields-list), or in a [field assignment](#field-assignment) rule,
it sets the value of some part of the hledger transaction corresponding the current CSV record, influencing the generated journal entry and hledger's output.
it sets the value of some part of the hledger transaction corresponding to the current CSV record, influencing the generated journal entry and hledger's output.
Note these field names (both kinds) are used only in CSV rules files,
though the hledger field names correspond to the hledger transaction parts described in Journal > [Transactions](#transactions).
though the hledger field names correspond to the hledger transaction parts described in [hledger manual > Journal](#transactions).
Here are the hledger field names available, and what happens when you assign values to them using a fields list or field assignment rule: