Hi Alberto, Great work! This was a much needed feature. Thank you for this contribution.
Subham from the community had spent some effort in doing the same and parked it when priorities changed. The issue he faced after the initial set of refactorings to remove ORM mappings of relationships across modules was the charges module which is coupled with loans and savings. The particular sub-problem where we had stopped was that regression in loan charges shouldn't impact savings test cases and regression in savings charges shouldn't impact loan test cases. In the dependency tree and future steps you shared, it's not clear how you solved it or how you're planning to solve that problem. Can you share your thoughts on this? With best regards, Avik Ganguly. On Mon, Dec 18, 2023 at 8:23 PM Jose Alberto Hernandez < josealbert...@gmail.com> wrote: > Hello to All! > > > As part of the Fineract modularization process, I have developed the > *fineract-savings* module and It's planned to be *released* in *January > 2024*. > > This change involves *many Java files to be relocated* (renamed) from > fineract-provider module to the new fineract-savings module, so the impact > and change logic is practically nothing > > There are other few relocations to the fineract-core module because those > classes are used in common > > So, the dependency tree will be: > > fineract-provider > | --- depends on: fineract-core > fineract-loan > fineract-investor > fineract-savings > > fineract-loan > | --- depends on: fineract-core > > fineract-investor > | --- depends on: fineract-core > > fineract-savings > | --- depends on: fineract-core > > > To Do: Sadly we can move yet all the Savings code to the final module due > there are other entity dependencies > > In the meantime that it is released we'll work in the next two modules: > Accounting and Organization > > Please feel free to let us know any comment, feedback or concern about > this. > > Thanks and Best Regards, Happy Holidays! > Alberto >
