Thanks Victor and Arthur. Currently the customization is in a state that would fit in the upstream code so that is why I have yet not submitted a ticket for it.
Regards. Wilfred. On Thu, 4 Jan 2024, 01:13 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. >> >
