Refactoring of forecast to budget
forecast better suited at budget, otherwise a single account would have a lot of overhead related to planning
adapt unit test to new api
move functionality internally as well
extract schedule value,
finally, another domain word I've missed
push new domain word through the domain
push new domain word through the domain
cleanup
found another domain word :). A schedule describes how and when a planned transaction is expected to take place
only call directly known members
Calculation depended a lot on the schedule
Calculation depended a lot on the schedule
Reuse common utilities for date functions
period always represents a period of complete days
Reusable in domain tests
Readable code and found a few more domain object capabilities
value objects ignore identity.
cleanups
Refactoring finished