Wednesday, August 26, 2020
3 changes · master
Enhancements to existing features
This improvement lets Odoo pass an optional loading preference through combined search-and-read operations. Businesses can avoid unnecessary display-name calculations in specific cases, improving performance for data-heavy processes without changing normal behavior.
Original PR description
The load parameter using 'classic_read' for method - read(fields, load='classic_read') it is computing name_get for each record. But what about if you don't want to optimize to avoid computing that value. You need to use 2 lines of code: records = self.search(...) records.read (..., load='') But there is a cleaner way using self.search_read(..., load='') But it was not supported the "load" parameter This change adds that support. cc @rco-odoo @odony @xmo-odoo
Businesses can now set a custom name for the Events Progressive Web App in each website's settings. If no custom name is provided, the app automatically uses the website name followed by “Events,” making branding clearer with minimal setup.
Original PR description
This commit adds a website-specific and customizable app name for the Events' Progressive Web Application, configurable through the website's settings. Defaults to '<website_name> Events'. X-original-commit: 423076ddf1da0fc61d9a18dc19bbbbf900e3dad6
The Planning Gantt view now keeps the employee list in the same order while users drag and drop schedule items. This reduces confusion by only refreshing the display order when the user next opens the relevant menu.
Original PR description
PURPOSE Currently, the way employees are sorted on the gantt view changes live, which is confusing because one second my employee is the first of the list, the next, he/she isn't anymore. SPEC The order in which employees are displayed on the gantt view should only be updated the next time the user opens these menus TASK 2129131