Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@somasorosdpc
Copy link
Contributor

Description

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.

@somasorosdpc somasorosdpc force-pushed the FINERACT-2201/Bug--Negative-numbers-in-case-of-progressive-interest-bearing-loans--reamortization branch 2 times, most recently from 37b475c to e5b0740 Compare March 7, 2025 18:22
@somasorosdpc somasorosdpc force-pushed the FINERACT-2201/Bug--Negative-numbers-in-case-of-progressive-interest-bearing-loans--reamortization branch from e5b0740 to faf0bd5 Compare March 11, 2025 09:47
@tamasszabo-dpc
Copy link
Contributor

LGTM

@adamsaghy adamsaghy merged commit a28b933 into apache:develop Mar 12, 2025
10 checks passed
@adamsaghy adamsaghy deleted the FINERACT-2201/Bug--Negative-numbers-in-case-of-progressive-interest-bearing-loans--reamortization branch March 12, 2025 12:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants