Monday, July 5, 2021
4 changes · master
Resolved issues and error corrections
This update prevents a supplier information view meant only for replenishment rules from appearing in the general Purchase Configuration menu. It avoids errors for users opening supplier information outside that specific replenishment context.
Original PR description
The commit 6eaa4a2ae3b12b244f4c4277ef9cbc172f492f0a introduced a new view on model supplier info. The issue is that this new view is meant to be used on supplier info as One2Many on stock.orderpoint and so contains some `parent.` relation. As no sequence has been set. This view replaced the original one in the Purchase Configuration menu. Leading to some error as `parent.` in not defined for standalone tree view. This commit set a sequence on this new view to ensure it is used only on the orderpoint form view. 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
This fix makes the Point of Sale interface properly show a blocking overlay while it is sending information to the server. This helps prevent users from interacting with the screen during processing, reducing duplicate actions or confusion.
Original PR description
Before this commit, the block UI component was not visible so the interface was not blocked when sending RPC (at least). After this commit, the block UI works correctly 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
This update prevents Odoo's web development tooling from mishandling installation paths that contain spaces. It reduces the risk of accidental file deletion during internal tooling operations, making developer workflows safer.
Original PR description
If $basepath in the tooling contained spaces, it could have dramatic consequences on the rm -rf command. We simply escape everything to avoid the problem.
This update restores consistent access to context values when Odoo evaluates expressions in the web client. It helps prevent action filters or domains from behaving incorrectly when they rely on fallback context values.
Original PR description
When the owl refactoring landed, we rewrote the pyjs evaluation system.
Then, we used the new system in the new code. In particular, the action
service uses it to evaluate the action domain.
But the previous code had a subtle behaviour in the special case of
evaluating domain: it added the context as a pydict object in itself, so
one could evaluate expression such as `context.get('a', 14)` to read the
value of a key in the context with a fallback.
With this commit, we uniformize this behaviour across all python
expression: the `context` key is now reserved, and used to access
anything in the current evaluation context.
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