Tuesday, July 5, 2022
3 changes · master
Enhancements to existing features
Odoo’s core data reading process was improved so it can postpone database updates and read more efficiently. This should improve performance and reliability across many business apps while tightening safeguards that keep in-memory and database data consistent.
Original PR description
The idea is to avoid flushing the fields to fetch in method `_read()`. This delays UPDATE queries, and makes the prefetching mechanism simpler and more effective. We do this by not overwriting the cache values by the values fetched from database. This simple idea allows to fetch more fields and more records without having to care about pending computations and updates. But it requires the cache consistency to be much more strict, because nothing will "fix" the cache inconsistencies "by chance". And it also requires pending updates to be present in cache.
Survey multiple-choice questions now display answer options in a more balanced layout, avoiding awkward uneven rows. Selection buttons stay clearly positioned at the top right, and one-question-per-page surveys use the available space better for easier answering.
Original PR description
Currently, in survey for single/multiple choice questions, the layout is not consistent. For example, if there are four choices available, the layout is 3-1 (3 small options in first row, 1 full…
Currently, in survey for single/multiple choice questions, the layout is not consistent. For example, if there are four choices available, the layout is 3-1 (3 small options in first row, 1 full width option in last row). Apart from that, if the string for options is long, radio / check box comes at the bottom right corner, which should always be at the top right corner. This commit does the following improvements: 1/ Improve the choices layout to make it beautiful. If there are 1,2 or 4 options, there will be 2 options in a single row, and otherwise there will be 3 options in a single row. 2/ The radio / check-box icon will be displayed in the top right corner regardless the length of option strings. 3/ In the 'One Page Per Question' layout, the MCQ questions will now occupy full width instead of the minimized layout, and instead of one option per row, it will now display the options as mention first point (2 options per row or 3 options per row). TaskID-2712296
Debug mode will automatically be disabled after a limited time, helping prevent technical field details from appearing during demos or webinars. This also ensures users leave debug mode after loading demo data, reducing confusion and keeping presentations cleaner.
Original PR description
Avoid staying in debug mode too long, polluting webinars with fields descriptions, etc. Leave debug mode once loading of demo data is done (main reason why demo are impacted by demo data) (e.g. Go to Settings > Load demo data in debug mode; after the refresh you should be out of debug mode) The duration is configurable "--debug-duration". opw-2830119 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr