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:
*[email protected] <[email protected]>*
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 <
[email protected]> 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 (<
> [email protected]>) 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.
>>
>

Reply via email to