Odoo Changelog — 2023-12-18

Monday, December 18, 2023

2 changes · master

Refactoring(2)

Code cleanup and technical improvements

[REF] l10n_**: Demo Data Cleanup

Coremasterl10n_account_edi_ubl_cii_testsl10n_aul10n_au_accountl10n_bel10n_be_accountl10n_hkl10n_hk_accountl10n_chl10n_ch_accountl10n_skl10n_sk_accountl10n_rol10n_ro_accountl10n_pll10n_pl_accountl10n_nll10n_nl_accountl10n_ltl10n_lt_accountl10n_mxl10n_mx_accountMedium

This change reorganizes country-specific localization modules so each country has one shared demo data package and separate accounting-specific modules. This reduces duplicate demo companies when multiple localization packages are installed, making testing and demonstrations cleaner and more consistent.

Original PR description

Auto Install ============ By having only one root module per country, containing minimal data and model changes, we can use that module to auto-install all localization for other modules. For…

Auto Install
============

By having only one root module per country, containing minimal data and model changes, we can use that module to auto-install all localization for other modules.
For instance, installing `l10n_xx`, `account` and `hr_payroll` will automatically install all the bridges required for the country `xx`.


Demo Data
=========

Up until now, we did not have any common demo data package for localization. This is an issue for localization having both accounting and hr packages, because these do not depend on each others.
It means that to have complete demo data individually, they need to define demo company in both cases.

This leads to duplication in demo companies for a single country when both packages are installed, which is not ideal for testing as it also means that demo data is split between multiple companies.

This commit will rename things a bit to bring a common demo data package for multiple localization.

`l10n_xx` as it is known today becomes `l10n_xx_account` (as it was all along an invoicing module).
`l10n_xx` is instead a new module containing the demo company data.

task-3555251

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

#localization#demo data#accounting#module cleanup

[REF] mail: simplify some discuss model insert

PR #146370

Coremastermailwebsite_livechat

This update streamlines how Odoo's Discuss and related chat features load conversation data. It reduces duplicated browser-side processing by using information already provided by the server, which should make the code easier to maintain without changing day-to-day user workflows.

Original PR description

Reduce LOCs in JS by relying more on server data to immediately insert in client-side modelling. In most cases the data were already complete enough.

#discuss#chat#maintenance

Auto Install ============ By having only one root module per country, containing minimal data and model changes, we can use that module to auto-install all localization for other modules. For instance, installing `l10n_xx`, `account` and `hr_payroll` will automatically install all the bridges required for the country `xx`. Demo Data ========= Up until now, we did not have any common demo data package for localization. This is an issue for localization having both accounting and hr packages, because these do not depend on each others. It means that to have complete demo data individually, they need to define demo company in both cases. This leads to duplication in demo companies for a single country when both packages are installed, which is not ideal for testing as it also means that demo data is split between multiple companies. This commit will rename things a bit to bring a common demo data package for multiple localization. `l10n_xx` as it is known today becomes `l10n_xx_account` (as it was all along an invoicing module). `l10n_xx` is instead a new module containing the demo company data. task-3555251 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr