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

doc: journal: fix account types regexps table rendering (#1573)

Browse Source
This commit is contained in:
Simon Michael 2021-06-16 10:09:15 -10:00
parent f30cea32b9
commit 2cba15a97d
1 changed files with 12 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
hledger/hledger.m4.md
View File

@ -2669,17 +2669,18 @@ If you happen to use common english top-level account names, you may
not need to declare account types, as they will be detected
automatically using the following rules:
| If name matches this [regular expression]: | account type is:
|----------------------------------------------|-----------------
| `^assets?(:|$)` | `Asset`
| `^(debts?|liabilit(y|ies))(:|$)` | `Liability`
| `^equity(:|$)` | `Equity`
| `^(income|revenue)s?(:|$)` | `Revenue`
| `^expenses?(:|$)` | `Expense`
| If account type is `Asset` and name does not contain this regular expression: | account type is:
|-------------------------------------------------------------------------------|-----------------
| `(investment|receivable|:A/R|:fixed)` | `Cash`
<!-- monospace to work around https://github.com/simonmichael/hledger/issues/1573 -->
```
If account's name matches this regular expression: | its type is:
------------------------------------------------------------------- | ------------
^assets?(:|$) |
and does not contain regexp (investment|receivable|:A/R|:fixed) | Cash
otherwise | Asset
^(debts?|liabilit(y|ies))(:|$) | Liability
^equity(:|$) | Equity
^(income|revenue)s?(:|$) | Revenue
^expenses?(:|$) | Expense
```
Even so, explicit declarations may be a good idea, for clarity and
predictability.