You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once we have a Journal parent object which sets the accounting period it makes no sense to have an idea of a "global" period. The period is per-journal, not per application. Obviously if an application that uses this library wants, they can use a single period everywhere, but it will have to be done in that case explicitly.
remove fallback to JournalPeriod when period not specified in LineItem scopes
remove fallback to JournalPeriod when period not specified in Account scopes
fallback to parent Journal when period not specified in LineItem scopes
fallback to parent Journal when period not specified in Account scopes
JournalPeriod remove support for global periodicity fallback
configs remove support for configuring global periodicity fallback
The text was updated successfully, but these errors were encountered:
Now that we have a `Journal` model (which "owns" `Account` models) we
should update our testing helpers to account for the journal instances
more explicitly. This PR does just that.
Also we add the notion of a 'current period' to `Journal` and remove the
notion of a globally configured "accounting period": a `Journal` now
controls what is the current accounting period in any given context for
objects which descend from it (accounts, line items, etc.). Later work
can further modify existing scopes to require that journal object to use
as a fallback when a more specific period is not needed (and to ensure
all e.g. ledger line items are always scoped to a specific journal).
Related to #16. Closes#19.
-----
Automated Test Results:
OK (191 tests, 319 assertions)
Once we have a
Journal
parent object which sets the accounting period it makes no sense to have an idea of a "global" period. The period is per-journal, not per application. Obviously if an application that uses this library wants, they can use a single period everywhere, but it will have to be done in that case explicitly.JournalPeriod
when period not specified inLineItem
scopesJournalPeriod
when period not specified inAccount
scopesJournal
when period not specified inLineItem
scopesJournal
when period not specified inAccount
scopesJournalPeriod
remove support for global periodicity fallbackconfigs
remove support for configuring global periodicity fallbackThe text was updated successfully, but these errors were encountered: