- Don't break before advancing 'starting_after' cursor
* Only save given year instead of breaking when not given year
- The 'next_starting_after' cursor now exists within 'info' object
- Creates per-wallet / per-account compliance for IRS Rev. Proc. 2024-28
* Obfuscated keymap now creates a unique indentifier per-wallet /
per-account where all trades, spends and income are now clearly
tied to their respective wallets / accounts.
- Removes support for anonymized ("universal pool") reports.
- Re-enables space after completion for plugin arguments
- Ignores internal/implementation files when completing
* Files must be within an 'internal'/'impl' directory
As said before; `lib_ledger` was meant to be a general abstraction to
any underlying CLI ledger.
But, between C++ `ledger` and Ledger Hardware Wallet, this abstraction
has become too confusing and counterproductive.
Since `hledger` will be the underlying implementation for the forseeable
future, all doubt should now be removed.
As said before; `lib_ledger` was meant to be a general abstraction to
any underlying CLI ledger.
But, between C++ `ledger` and Ledger Hardware Wallet, this abstraction
has become too confusing and counterproductive.
Since `hledger` will be the underlying implementation for the forseeable
future, all doubt should now be removed.
Since modules are included upon build type, if a build doesn't support
a feature then that feature's dependencies will not be available.
This commit will give notice of those missing dependencies.
Since inception, the intent was to abstract the "interface" to allow for
a general-purpose CLI accounting ledger. However, there appears to be
confusion about whether the underlying implementation is `ledger`
accounting software or `hledger` accounting software.
So, making it clearer that it's `hledger` accounting software (although,
will continue to keep the `ledger` command for backwards-compatibility).
Since inception, the intent was to abstract the "interface" to allow for
a general-purpose CLI accounting ledger. However, there appears to be
confusion about whether the underlying implementation is `ledger`
accounting software or `hledger` accounting software.
So, making it clearer that it's `hledger` accounting software (although,
will continue to keep the `ledger` command for backwards-compatibility).
- Adds plugin type support
* Adds pseudo-paths to help usage
* Adds arg parsing of given plugin name
- Prepended pseudo-paths will use repo or custom plugin
