Aaron Bohy
4c5b867ff6
Before this commit, the rendering context of kanban and form views was the instance of the KanbanRecord and FormRenderer, respectively. As a consequence, a lot of implementation details (e.g. "props", "__owl__", any Class method...) were available. This wasn't what we want. The door being left open, people went through, and in 16.0, several kanban and form archs contain(ed) such use of undesired "features". With this commit, we restrict the rendering context of those two views. In kanban views, it contains what has been historically available (e.g. "record", "widget", "kanban_color"...). In form views, nothing is available since the only dynamic part in those archs is the attrs, which aren't evaluated by the rendering engine. To do that, we use `t-call-context` owl directive. When using this directive, the rendering context is the given one, + `this`. So the component instance is still available, but through the `this` keyword. We can thus use it in our compilers, to make them work as before. Note that `this` can never be used in an arch directly. Task 3085357 closes odoo/odoo#106045 Related: odoo/enterprise#34493 Signed-off-by: Lucas Perais (lpe) <lpe@odoo.com>
Odoo
Odoo is a suite of web based open source business apps.
The main Odoo Apps include an Open Source CRM, Website Builder, eCommerce, Warehouse Management, Project Management, Billing & Accounting, Point of Sale, Human Resources, Marketing, Manufacturing, ...
Odoo Apps can be used as stand-alone applications, but they also integrate seamlessly so you get a full-featured Open Source ERP when you install several Apps.
Getting started with Odoo
For a standard installation please follow the Setup instructions from the documentation.
To learn the software, we recommend the Odoo eLearning, or Scale-up, the business game. Developers can start with the developer tutorials