0f1cbef9a8
This renames RawTransaction -> Posting and Entry -> LedgerTransaction, plus a bunch more cleanups for consistency. So while ledger 3 has transactions containing postings, and so do we when speaking to users, internally we call ledger 3's transactions LedgerTransaction, and we keep our old Transaction type as well, because it's useful and used all over the place. To review: - ledger 2 had Entrys containing Transactions. - hledger 0.4 had Entrys containing RawTransactions, and Transactions which are a RawTransaction with its parent Entry's info added. Transactions are what we most work with when reporting and are ubiquitous in the code and docs. - ledger 3 has Transactions containing Postings. - hledger 0.5 now has LedgerTransactions containing Postings, with Transactions kept as before (a Posting plus it's parent's info). These could be named PartialTransactions or TransactionPostings, but it gets too verbose and obscure for devs and users.
39 lines
1.0 KiB
Haskell
39 lines
1.0 KiB
Haskell
{-|
|
|
|
|
The Ledger package allows parsing and querying of ledger files.
|
|
It generally provides a compatible subset of C++ ledger's functionality.
|
|
|
|
-}
|
|
|
|
module Ledger (
|
|
module Ledger.Account,
|
|
module Ledger.AccountName,
|
|
module Ledger.Amount,
|
|
module Ledger.Commodity,
|
|
module Ledger.Dates,
|
|
module Ledger.LedgerTransaction,
|
|
module Ledger.Ledger,
|
|
module Ledger.Parse,
|
|
module Ledger.RawLedger,
|
|
module Ledger.Posting,
|
|
module Ledger.TimeLog,
|
|
module Ledger.Transaction,
|
|
module Ledger.Types,
|
|
module Ledger.Utils,
|
|
)
|
|
where
|
|
import Ledger.Account
|
|
import Ledger.AccountName
|
|
import Ledger.Amount
|
|
import Ledger.Commodity
|
|
import Ledger.Dates
|
|
import Ledger.LedgerTransaction
|
|
import Ledger.Ledger
|
|
import Ledger.Parse
|
|
import Ledger.RawLedger
|
|
import Ledger.Posting
|
|
import Ledger.TimeLog
|
|
import Ledger.Transaction
|
|
import Ledger.Types
|
|
import Ledger.Utils
|