Friday, January 20, 2023
3 changes · master
Code cleanup and technical improvements
This change moves a website template loading test and its test-only data into the dedicated test website module. It keeps the main website module cleaner by separating internal test assets from production module content, with no expected impact on users.
Original PR description
When the QWeb `<template>` loading test was introduced at [1], the `test_website` module did not exist yet, see [2]. This commit moves that test and its related data file to `test_website` to remove the `fake data` noise from the `website` module. That's one of the two purpose of this `test_website` module: - Avoid noising the website module with test only data & code - Encapsulate in a lighter module the module operations tests, but it's not really the case anymore as those tests are now standalone tests. See manifest for more details. [1]: https://github.com/odoo/odoo/commit/9cd982bcc811cacb42f5c08db139043d2734b891 [2]: https://github.com/odoo/odoo/commit/ef03db9edd9472201cb2c08a32d20ff0f33a5fdf
Spreadsheet dashboards now use a clearer internal name for the stored spreadsheet data instead of the vague legacy name. This makes the feature easier to maintain and integrate without changing the dashboard experience for users.
Original PR description
Up until now, the collaborative expected a field named `raw` containing the serialized json data. This is historic and appeared because the field containing the existing field `raw` on `document.document` contained this data. The name `raw` is meaningless. Now the collaborative expects and will call a method called `get_spreadsheet_data` --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The spreadsheet collaboration code now uses a clearer name for stored spreadsheet data instead of the vague legacy "raw" field. This is an internal cleanup that makes the feature easier to maintain while preserving the existing spreadsheet dashboard behavior for users.
Original PR description
Up until now, the collaborative expected a field named `raw` containing the serialized json data. This is historic and appeared because the field containing the existing field `raw` on `document.document` contained this data. The name `raw` is meaningless. Now the collaborative expects and will call a method called `get_spreadsheet_data`