Thanks Ed. I will follow this doc and liaise with Aleks if I have any questions.
Regards. Wilfred. On Thu, 4 Jan 2024, 07:56 Ed Cable, <edca...@mifos.org> wrote: > Wilfred, > > You can also utilize the new custom modules feature which helps to achieve > the goals that Mugabe outlined in his last post around being able implement > custom changes without leading to conflict and difficulty in maintaining > compatibility with upstream. > > https://fineract.apache.org/docs/current/#_custom_modules > > @Aleksandar Vidakovic <chee...@monkeysintown.com> can share more details > on using the custom modules approach. > > Thanks, > > Ed > > On Wed, Jan 3, 2024 at 2:31 PM Magezi Arthur <artmag...@gmail.com> wrote: > >> Hello Wilfred, >> Additionally you could add a module for holding all your custom changes >> and just override the core functionalities. >> This helps you properly isolate your customizations from the core >> modules, hence allowing you to always fetch the latest versions with >> limited or no conflicts. >> >> On the other hand, contributing back would be easy since your custom code >> won’t be too entangled with your core. >> >> Happy new year. >> >> *MUGABE MAGEZI ARTHUR* >> Software Developer and >> Process Management Consultant >> emails: >> *artmag...@gmail.com <artmag...@gmail.com>* >> Mob: +256704901261 >> facebook: Magezi Arthur >> Skype: marthur26 >> >> The Struggle the doesn't break you will make you, if you hold a little >> longer under that fire you will certainly come out as Gold >> >> >> On Thu, 4 Jan 2024 at 01:14, VICTOR MANUEL ROMERO RODRIGUEZ < >> victor.rom...@fintecheando.mx> wrote: >> >>> Hello Wilfred, >>> >>> My response for suggesting the “best way” >>> >>> 1. Write a Jira ticket with the change/feature requested, socialize it >>> on this list and upstream your changes as a PR to the development branch of >>> Apache Fineract. >>> >>> If the feature is not shared or sent back to the community (and >>> technical, legal reasons for not doing this) the code could be out of sync >>> and rebased by changes in the development branch and everyone must agree on >>> this in order to maintain that legacy piece of code. >>> >>> Regards >>> >>> Victor >>> >>> >>> El mié, 3 ene 2024 a las 15:18, Kigred Developer (< >>> kigred.develo...@gmail.com>) escribió: >>> >>>> Hello Devs, >>>> >>>> Happy New Year. >>>> >>>> What is the best way to customize fineract and still be able to use new >>>> code updates without breaking one's customised code? >>>> >>>> For example I am trying to make changes that enable users to purchase >>>> shares using a clients savings funds (it essentially a transfer >>>> transaction) but I want to use the other modules just the way they are and >>>> also be able to pull changes when fineract 1.9 is release without losing my >>>> customisations. >>>> >>>> What is the best way to do this? >>>> >>>> Regards. >>>> Wilfred. >>>> >>> > > -- > *Ed Cable* > President/CEO, Mifos Initiative > edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649 > > *Collectively Creating a World of 3 Billion Maries | *http://mifos.org > <http://facebook.com/mifos> <http://www.twitter.com/mifos> > >
