FINERACT-2412: Full term tranche - Schedule handling and Calculations

[mariiaKraievska]

Description

Describe the changes made and why they were made. (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 our guidelines
• 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 our 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
• This PR must not be a "code dump". Large changes can be made in a branch, with assistance. Ask for help on the developer mailing list.

Your assigned reviewer(s) will follow our guidelines for code reviews.

[Aman-Mittal]

I think this LoanAplicationBuilder Logic must be extracted to an new helper function. So that it is easier to read.

and group this chaining maybe like this?

// Loan basics
.currency(...)
.principal(...)
.repaymentsStartingFromDate(...)

// Term & frequency
.loanTermFrequency(...)
.numberOfRepayments(...)
.repaymentEvery(...)
.repaymentPeriodFrequencyType(...)

// Interest configuration
.interestRatePerPeriod(...)
.annualNominalInterestRate(...)
.interestRatePeriodFrequencyType(...)
.interestMethod(...)

// Day count conventions
.daysInMonthType(...)
.daysInYearType(...)
.daysInYearCustomStrategy(...)

// Flags & options
.isDownPaymentEnabled(false)
.allowPartialPeriodInterestCalculation(...)

// Technical
.mc(mc)

[mariiaKraievska]

Done

[Aman-Mittal]

Code wise seems ok, Not reviewed based on e2e tests due to my lack of functional knowlegede.

Message to Maintainer: Please cross-check the tests before merge