I think this would be cool since there may be students that may not want to pay all the debt upfront but instead pay a part and then pay another part later.
If we don't provide this we would be leaving this use case out of the app
Complication
One major thing I am a bit concerned about when thinking about implementing this is the fact that a single student can have multiple debts.
So partial payment would involve having to take into account the fact that students that have multiple debts, should cover them from oldest to newest.
Initial approach
We need to check up to which debt the student would be paying. And thus break that one into two separated debts, one paid and another unpaid if they don't cover for it completely.
Must also take into account that we will have to create multiple payments, one for each StudentDebt that is fulfilled. This in favor of keeping the uniqueness of paymentId across StudentDebt entities. (Not sure whether this is the right call Spinoff somewhere else: #13 ).
Break student debts into two debts, one of them is paid and the other is to be paid. Old debt can definitely be deleted since the new debts are the representation of the previous debt
Pay debts partially
I think this would be cool since there may be students that may not want to pay all the debt upfront but instead pay a part and then pay another part later.
If we don't provide this we would be leaving this use case out of the app
Complication
One major thing I am a bit concerned about when thinking about implementing this is the fact that a single student can have multiple debts.
So partial payment would involve having to take into account the fact that students that have multiple debts, should cover them from oldest to newest.
Initial approach
paymentIdacrossStudentDebtentities. (Not sure whether this is the right call Spinoff somewhere else: #13 ).Mock
[WIP]