diff options
| author | Lucas Perais (lpe) <lpe@odoo.com> | 2019-06-04 13:29:58 +0000 |
|---|---|---|
| committer | Vincent Schippefilt <vsc@odoo.com> | 2019-07-24 12:21:59 +0000 |
| commit | fc5878ecc668ee83cd1a374474f0b21bf6a51940 (patch) | |
| tree | b08e064a72f84d4fb14a0b5560ae1fd142c05563 /odoo/modules/module.py | |
| parent | 8be4567ae8f6b0388206c091590278ef11a2df21 (diff) | |
[IMP] base, web: static xml templates support serverside inheritance
QWeb templates that show up in the 'qweb' key of a module's manifest
now support server side inheritance and xpath evaluation
QWeb templates that show up in the xmlDependencies of a JS widget are not
impacted at all by theses changes, as they are served through the
Werkzeug sharedMiddleware
A similar syntax than ir.ui.view has been implemented in the QWeb templates
- each template must have a root node, whatever tag works
- the root node of a template must have a t-name containing the name of the template
The name -- without the module's name -- may contain dots pretty much anywhere
Though what is recommended is only underscores in template names
- if a template is to inherit from a parent, the root node has a t-inherit directive
containing either the full name of the template it inherits from which is module_name.template_name
or the name of the template, no module name necessary, if the parent template is in the same module
- there are 2 modes of inheriting
primary: copy the behavior of the parent into the template
extension: modifies the parent in place
Task: 1999528
closes odoo/odoo#33892
Signed-off-by: VincentSchippefilt <VincentSchippefilt@users.noreply.github.com>
Co-authored-by: Julien Mougenot <jum@odoo.com>
Co-authored-by: Lucas Perais <lpe@odoo.com>
Diffstat (limited to 'odoo/modules/module.py')
0 files changed, 0 insertions, 0 deletions
