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

This commit is contained in:
Simon Michael 2021-06-16 10:09:15 -10:00
parent f30cea32b9
commit 2cba15a97d

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