Daily updates from Odoo
Tuesday, August 29, 2023
5 changes
Code cleanup and technical improvements
This update removes several older shared service components and updates affected apps to use the newer approach. It helps keep the platform easier to maintain while preserving behavior across Documents, HR, Knowledge, Barcode, VoIP, and mobile features.
Original PR description
task 3439226
A shared web data component now supports saving and reloading a record immediately after certain updates. This streamlines workflows in areas such as appraisals, payroll, manufacturing work orders, and website knowledge by ensuring changes are persisted right away when needed.
Original PR description
[REF] web: RelationalModel: add option to save after update This commit adds an option to save the record after an update. When the save option is set to true, the record will be saved and reload after the update. Note that, the onChange is not done in this case.
This is much more robust and faster than relying on arbitrary number of animation frames. https://github.com/odoo/odoo/pull/133333
Original PR description
This is much more robust and faster than relying on arbitrary number of animation frames. https://github.com/odoo/odoo/pull/133333
Odoo Enterprise now standardizes date handling by replacing older Moment.js usage with Luxon across several applications. This reduces duplicated technology in the product and helps lighten web assets without changing business workflows.
Original PR description
luxon and moment are both used in the solution, but these two libraries facilitate the manipulation of dates. It was decided to replace all uses of moment with luxon so we can then remove moment.js from the code and lighten the assets. task-3391739 PR Community : https://github.com/odoo/odoo/pull/133144
Account report session handling was simplified by replacing several internal options with a single on/off setting. This reduces unnecessary complexity while preserving the existing behavior users rely on when reports remember or ignore saved options.
Original PR description
Account reports save options into the session so users don't lose them when reloading the page.To prevent some reports to use those session options we used the 'ignore_session' variable. The 'ignore_session' could have 3 values: - 'read' to prevent the reading of session options - 'write' to prevent the writing of session options - 'both' to prevent reading and writing of session options The thing is that there is not real usage for those 3 cases. In practice, the session options are completely ignored (read and write) or never ignored. The distinction between 'read' and 'write' is then useless. This all means that we can simplify that variable by making it a boolean instead.