Thibault Delavallée 4ba77c52f5 [FIX] phone_validation: fix MRO issue with phone.validation.mixin ...

Issue is that when a model inherits from phone.Validation.mixin, then from
mail.thread.phone (which inherits from phone.validation.mixin) we have
an issue :

TypeError: Cannot create a consistent method resolution
order (MRO) for bases BaseModel, base, mail.thread, phone.validation.mixin,
mail.thread.phone

As fixing it could be complicated we have a way to avoid it: move conflicting
code as it is used only in mail.thread.phone .

In this commit we also import a file forgotten at d2809cbd94 which triggers
the issue itself.

Task 2063049 (bug spotted)
Task 2061765 (triggering the issue)

closes odoo/odoo#36580

Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>

2019-09-09 15:54:45 +00:00

..

__init__.py

[FIX] phone_validation: fix MRO issue with phone.validation.mixin

2019-09-09 15:54:45 +00:00

mail_thread_phone.py

[FIX] phone_validation: fix MRO issue with phone.validation.mixin

2019-09-09 15:54:45 +00:00

phone_blacklist.py

[IMP] phone_validation: add blacklist mechanism

2019-08-12 12:00:22 +00:00

phone_validation_mixin.py

[FIX] phone_validation: fix MRO issue with phone.validation.mixin

2019-09-09 15:54:45 +00:00

res_partner.py

[IMP] phone_validation, crm: move onchange on phone fields

2019-09-09 12:45:47 +00:00