Contributors mailing list archives

contributors@odoo-community.org

Re: Overwriting a method in OCA module.

by "Kitti U." <kittiu@ecosoft.co.th> - 16/09/2015 12:44:11
Very much appreciated everyone, it is crystal clear now.

Just want to ask, if you think this kind of case should post to OCA contribution standard? Or is it just matter of preferences?

And if it would, should we have 1 monkey-patch module for the original module being overwritten?
(i.e., account_voucher_monkeypatch)

** but this will provide some small chance to have duplicated monkeypatch module in different projects.

Thanks again
Kitti

On Tue, Sep 15, 2015 at 10:53 PM, Nhomar Hernandez <nhomar@vauxoo.com> wrote:

On Tue, Sep 15, 2015 at 4:07 AM, Kitti U. <kittiu@ecosoft.co.th> wrote:
So, we will have 1 monkey patch addon for each Project? i.e., account-invoicing_monkeypatch, sale-workflow_monkeypatch, etc...

Hello Kitty.

The monkey patch can be by functionality even by method.

The point of th monkey patch is that with simple correct the py file you will use quickly the original one in seconds.

And don't forget make alwas the PR to odoo/odoo itlesf in order to ensure in some moment do not need the monkey patch.

We apply this monkey patches temporarly when issues comes fron OPW also.

We called the "*_unfuck" modules.

Which if you look in the blame for the model/*.py it is empty just because we just receive the patch on odoo/odoo some weeks ago!. But the module stais there doing nothing until we make a major release, and everything was moves smothly.

I hope it helps.

--
Nhomar Hernandez
CEO Vauxoo.
Twitter: @nhomar
Odoo Gold Partner
Móvil Venezuela:
+58 4144110269
Móvil México:
+52 1 4773933942

_______________________________________________
Mailing-List: http://odoo-community.org/groups/oca-contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe




--
Mobile: +66-(0)8-1841-7480
Your ERP Partner => www.ecosoft.co.th