FINERTACT-1981: Advanced payment allocation fixes for Loan Schedule#3611
Conversation
5f556c5 to
711d89f
Compare
Integration Test case added |
There was a problem hiding this comment.
Please change the description accordingly what the test is testing
There was a problem hiding this comment.
Done!
There was a problem hiding this comment.
Please throw unique error code supported.only.for.progressive.loan.schedule.handling is already been used elsewhere for other purposes!
There was a problem hiding this comment.
Done!
...org/apache/fineract/integrationtests/AdvancedPaymentAllocationLoanRepaymentScheduleTest.java
Outdated
Show resolved
Hide resolved
adamsaghy
left a comment
There was a problem hiding this comment.
Please see my comments!
711d89f to
3417d61
Compare
Comments resolved |
b55a57b to
2ccefdf
Compare
|
@josehernandezfintecheandomx Please check the failing tests! |
96d7a0f to
b69f97d
Compare
6d3face to
3cf4b53
Compare
|
@josehernandezfintecheandomx Please check and fix the failing test cases! |
3cf4b53 to
9392b05
Compare
There was a problem hiding this comment.
For backward compatibility, the loan schedule type is optional. So it might not be sent, in that case the CUMULATIVE is the fallback default value. You might wanna mimic that behaviour here as well.
9392b05 to
fb2774a
Compare
fb2774a to
c15540c
Compare
…essive loan disbursement handling
Description
Advanced payment allocation should only support Progressive loan disbursement handling, so we needed to add a validation in the API
Ignore if these details are present on the associated Apache Fineract JIRA ticket.
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!
Write the commit message as per https://github.com/apache/fineract/#pull-requests
Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.
Create/update unit or integration tests for verifying the changes made.
Follow coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions.
Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/legacy-docs/apiLive.htm with details of any API changes
Submission is not a "code dump". (Large changes can be made "in repository" via a branch. Ask on the developer mailing list for guidance, if required.)
FYI our guidelines for code reviews are at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide.