hledger/hledger-lib/Hledger/Reports
Stephen Morgan 74f0f37fb3 imp: queries: Allow regular expression depth queries
Previously depth-limiting was universal across all accounts, e.g. all
accounts are clipped to depth 2. However, sometimes you want certain
accounts clipped to a different depth than others, e.g. all expenses to
depth 3, while all assets to depth 2. This commit enables depth-limiting
to optionally include a regular expression, which limits the accounts it
applies to.

More than one depth limit can be passed, and they are applied to each
account name by the following rules:
- If one or more regular-expression depth limit applies, use the
  most specific one
- If no regular-expression depth limits apply, and a flat depth limit is
  supplied, use that
- Otherwise, do not do any depth limiting

For example, this will clip all accounts matching "assets" to depth 3,
all accounts matching "expenses" to depth 2, and all other accounts to
depth 1.
--depth assets=3 --depth expenses=2 --depth 1
2024-12-03 08:33:21 -10:00
..
AccountTransactionsReport.hs cli: Commands.Aregister: implement --invert option 2024-10-23 21:55:24 -10:00
BalanceReport.hs imp: queries: Allow regular expression depth queries 2024-12-03 08:33:21 -10:00
BudgetReport.hs dev: refactor table rendering code 2024-06-12 05:01:48 +01:00
EntriesReport.hs imp: partial/inferred dates are flexible, full dates are not (#1982) 2023-02-17 07:24:19 -10:00
MultiBalanceReport.hs imp: queries: Allow regular expression depth queries 2024-12-03 08:33:21 -10:00
PostingsReport.hs imp: queries: Allow regular expression depth queries 2024-12-03 08:33:21 -10:00
ReportOptions.hs imp: queries: Allow regular expression depth queries 2024-12-03 08:33:21 -10:00
ReportTypes.hs dev: fix DisplayName's off-by-one indent value, noted in #2246 2024-10-08 23:11:57 -10:00