Monday, March 1, 2021
3 changes · master
Enhancements to existing features
When users open the app list from Accounting to look for a localization, the extra category search panel is now hidden. This reduces visual clutter and makes it easier to focus on the relevant localization options.
Original PR description
The search panel showing app categories in the app list is unnecessary when opening the list with the context of searching for a localization. This will change it so that panel is hidden in this case. task id #2370971 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update improves Odoo's automated testing process by allowing certain test groups to run in a required order. It helps ensure upgrade-related checks run reliably and reduces false failures in internal quality validation.
Original PR description
We have some tests in odoo/upgrade that are sensitive to the order on which they are executed. Specifically: IntegrityCase tests need to be run after all UpgradeCase tests across all Odoo modules. To support this we implemented a sorting mechanism for tests based on the test_sequence class attribute. This is intended to be used by meta cases, not by individual tests. 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
Odoo now treats fields used for model inheritance in a more consistent way when filtering records. This helps ensure that searches return the same results whether users search inherited fields directly or through their linked parent record, without weakening existing access rules.
Original PR description
The field that supports inheritance should be auto_join=True. This guarantees that searching on an inherited field (X) or its explicit related expression (foo_id.X) gives the same query. Note that adding auto_join=True on that field does not weakens the model's security, since searching on the model automatically injects the parent model's security rules into the query (see _apply_ir_rules).