lcreid
commented
7 years ago The first cut implementation simply reduces the amount of each invoice allocation, starting at the end, if the amount_available is less than zero. This meets the intent. I don't think we actually have to do all the other adjustments from Issue #65, since the invoice_amount doesn't actually change.
This implementation has a few caveats:
- It could be optimized a lot, possibly by taking advantage of Rails' totalling of associations
- The sorting needed to be improved, but I did that
Validations (loosely speaking) for Cf0925 must include, when there is a change to the Part A or Part B amount:
Iterate through all Invoices for the Cf0925, and do the same validations as if the invoice amount had changed, as described in Issue #65.