FINERACT-2477: Refactor SavingsAccountTransactionsApiResource command…#5543
Conversation
|
@SamaSVM check the error in the Backward compatibility logs |
… dispatch to switch expressions
8c631f2 to
7cc6746
Compare
| @@ -179,30 +175,17 @@ public String transaction(@PathParam("savingsId") final Long savingsId, @QueryPa | |||
| final String apiRequestBodyAsJson) { | |||
| final CommandWrapperBuilder builder = new CommandWrapperBuilder().withJson(apiRequestBodyAsJson); | |||
|
|
|||
There was a problem hiding this comment.
I think for refractor it will be a better approach to create separate helper functions so that it will maintain separation of concern and make these code more modular
There was a problem hiding this comment.
That’s a good point. However, I implemented the task according to its current description and requirements. I’m not sure what future changes are planned for the project or how they might be affected by my implementation.
There was a problem hiding this comment.
Hi, @SamaSVM It is the ticket created based on this PR https://github.com/apache/fineract/pull/5465/changes by @Saifulhuq01,
As his feature is not currently merge yet it will cause direct conflict. Maybe you should wait a bit for this?
@Saifulhuq01 I have linked your tickets as dependent state.
There was a problem hiding this comment.
Hi, @SamaSVM It is the ticket created based on this PR https://github.com/apache/fineract/pull/5465/changes by @Saifulhuq01, As his feature is not currently merge yet it will cause direct conflict. Maybe you should wait a bit for this?
@Saifulhuq01 I have linked your tickets as dependent state.
@Aman-Mittal Thanks for linking the tickets. @SamaSVM My force debit logic is fixed and awaiting final review from the maintainers on #5465. I will let you know the second it merges so you can proceed with your refactor.
Description
Refactored the SavingsAccountTransactionsApiResource logic.
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!
Your assigned reviewer(s) will follow our guidelines for code reviews.