Odoo Changelog — 2023-05-05

Friday, May 5, 2023

5 changes · master

Refactoring(5)

Code cleanup and technical improvements

[REF] mail: simplify message template

PR #120550

Coremastermail

The mail message layout was simplified to reduce duplicated code between viewing and editing messages, making it easier to maintain. It also corrects small visual issues so message editing and option menus behave more consistently for users.

Original PR description

Simplify template so there are less code duplication between editing state and non-editing state.

Also fixes following small style issues:
- missing opacity-25 when editing message of others
- expanded options of message come on top of jump present alert

#messaging#templates#user-interface

[REF] mail: move channel commands to discuss folder

PR #120429

Coremastermailim_livechat

The mail and live chat code has been reorganized so discussion channel command logic sits with the Discuss-related components. This is an internal cleanup that should make future maintenance easier without changing the user experience.

Original PR description

Part of task-3265211

#mail#discuss#livechat#maintenance

[REF] spreadsheet: move pivot/list dataSources to UI plugin

PR #120136

Coremasterspreadsheet

Spreadsheet pivot tables, lists, and charts now manage their temporary data connections in the user interface layer instead of the shared document core. This keeps document data cleaner, reduces unnecessary internal mapping, and helps avoid user-specific data details being stored or exchanged where they do not belong.

Original PR description

Before this commit, the pivot's dataSources were managed by the core plugin Pivot/ListCorePlugin. This didn't make sense since dataSources aren't core data: they are neither exported nor imported…

Before this commit, the pivot's dataSources were managed by the core plugin
Pivot/ListCorePlugin. This didn't make sense since dataSources aren't core data:

they are neither exported nor imported
they can be different for each user (their ids were generated via uuidv4
at import)
managing them required to handle local command in the core plugin
Moved the dataSources management to the UI plugin Pivot/ListUIPlugin and moved
the relevant getters inside this plugin. Changed the ids of the dataSources
to be the same as the pivot's id + a prefix, to avoid having to maintain a
mapping pivot/listId <=> dataSourceId .

This commit also removes the dataSourceId from the INSERT_PIVOT/LIST
command, which have no place here since this is a core command and the
dataSources are now a pure UI concept.

This is slighly more tricky for pivots than for lists, because the datasource need to
be loaded before the INSERT_PIVOT command to fetch the table structure.
The component dispatching the command need to make sure it creates a
dataSource with the id given by the getter getPivotDataSourceId,
or else the dataSource will be loaded twice.

Task: [3293491](https://www.odoo.com/web#id=3293491&menu_id=4720&cids=1&action=333&active_id=2328&model=project.task&view_type=form)



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

[REF] spreadsheet: move pivot/list dataSources to UI plugin

PR #40546

Enterprisemasterdocuments_spreadsheetspreadsheet_edition

Spreadsheet pivot tables and lists now keep temporary data source details in the user interface layer instead of the shared spreadsheet core. This reduces unnecessary internal complexity and helps keep collaboration and imports more consistent without changing expected end-user features.

Original PR description

Before this commit, the pivot's dataSources were managed by the core plugin
`Pivot/ListCorePlugin`. This didn't make sense since dataSources aren't core data:

- they are neither exported nor imported
- they can be different for each user (their ids were generated via uuidv4
at import)
- managing them required to handle local command in the core plugin

Moved the dataSources management to the UI plugin `Pivot/ListUIPlugin` and moved
the relevant getters inside this plugin. Changed the ids of the dataSources
to be the same as the pivot's id + a prefix, to avoid having to maintain a
mapping `pivot/listId` <=> `dataSourceId` .

This commit also removes the dataSourceId from the `INSERT_PIVOT/LIST`
command, which have no place here since this is a core command and the
dataSources are now a pure UI concept.

This is slighly more tricky for pivots than for lists, because the datasource need to
be loaded before the `INSERT_PIVOT` command to fetch the table structure.
The component dispatching the command need to make sure it creates a
dataSource with the id given by the getter `getPivotDataSourceId`,
or else the dataSource will be loaded twice.

Task: [3293491](https://www.odoo.com/web#id=3293491&menu_id=4720&cids=1&action=333&active_id=2328&model=project.task&view_type=form)

[REF] pos*: adapt assets bundle name to community changes

PR #40502

Enterprisemasterl10n_de_pos_certl10n_de_pos_res_certl10n_mx_edi_pospos_hr_mobilepos_iotpos_l10n_sepos_preparation_displaypos_restaurant_iotpos_settle_due

Several Point of Sale-related modules were updated to use the latest shared asset bundle naming from the core Odoo platform. This keeps these apps aligned with underlying platform changes and helps ensure their screens, integrations, and tests continue loading the right resources.

Original PR description

pos*: l10n_de_pos_cert, l10n_de_pos_res_cert, l10n_mx_edi_pos, pos_hr_mobile, pos_iot, pos_l10n_se, pos_preparation_display, pos_restaurant_iot, pos_settle_due

Linked to: odoo/odoo#120070

#point-of-sale#assets#maintenance

Simplify template so there are less code duplication between editing state and non-editing state. Also fixes following small style issues: - missing opacity-25 when editing message of others - expanded options of message come on top of jump present alert

Before this commit, the pivot's dataSources were managed by the core plugin Pivot/ListCorePlugin. This didn't make sense since dataSources aren't core data: they are neither exported nor imported they can be different for each user (their ids were generated via uuidv4 at import) managing them required to handle local command in the core plugin Moved the dataSources management to the UI plugin Pivot/ListUIPlugin and moved the relevant getters inside this plugin. Changed the ids of the dataSources to be the same as the pivot's id + a prefix, to avoid having to maintain a mapping pivot/listId <=> dataSourceId . This commit also removes the dataSourceId from the INSERT_PIVOT/LIST command, which have no place here since this is a core command and the dataSources are now a pure UI concept. This is slighly more tricky for pivots than for lists, because the datasource need to be loaded before the INSERT_PIVOT command to fetch the table structure. The component dispatching the command need to make sure it creates a dataSource with the id given by the getter getPivotDataSourceId, or else the dataSource will be loaded twice. Task: [3293491](https://www.odoo.com/web#id=3293491&menu_id=4720&cids=1&action=333&active_id=2328&model=project.task&view_type=form) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Before this commit, the pivot's dataSources were managed by the core plugin `Pivot/ListCorePlugin`. This didn't make sense since dataSources aren't core data: - they are neither exported nor imported - they can be different for each user (their ids were generated via uuidv4 at import) - managing them required to handle local command in the core plugin Moved the dataSources management to the UI plugin `Pivot/ListUIPlugin` and moved the relevant getters inside this plugin. Changed the ids of the dataSources to be the same as the pivot's id + a prefix, to avoid having to maintain a mapping `pivot/listId` <=> `dataSourceId` . This commit also removes the dataSourceId from the `INSERT_PIVOT/LIST` command, which have no place here since this is a core command and the dataSources are now a pure UI concept. This is slighly more tricky for pivots than for lists, because the datasource need to be loaded before the `INSERT_PIVOT` command to fetch the table structure. The component dispatching the command need to make sure it creates a dataSource with the id given by the getter `getPivotDataSourceId`, or else the dataSource will be loaded twice. Task: [3293491](https://www.odoo.com/web#id=3293491&menu_id=4720&cids=1&action=333&active_id=2328&model=project.task&view_type=form)