NextERP/documentation
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[FW][FIX] contributing/coding_guidelines: remove mention to assets.xml

Browse Source 
We no longer load assets by xml files, but we use __manifest__.py for that.

closes odoo/documentation#3778

Forward-port-of: odoo/documentation#3720
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
This commit is contained in:
poma-odoo 2023-03-09 08:35:52 +01:00 committed by GitHub
parent 497f7660f3
commit 75a102323b
1 changed files with 2 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
content/contributing/development/coding_guidelines.rst
View File

@ -88,15 +88,13 @@ Concerning *views*, backend views should be split like models and suffixed
by ``_views.xml``. Backend views are list, form, kanban, activity, graph, pivot, ..
views. To ease split by model in views main menus not linked to specific actions
may be extracted into an optional ``<module>_menus.xml`` file. Templates (QWeb
pages used notably for portal / website display) and bundles (import of JS and
CSS assets) are put in separate files. Those are respectively
``<model>_templates.xml`` and ``assets.xml`` files.
pages used notably for portal / website display) are put in separate files named
``<model>_templates.xml``.
.. code-block:: text
addons/plant_nursery/
|-- views/
| | -- assets.xml (import of JS / CSS)
| | -- plant_nursery_menus.xml (optional definition of main menus)
| | -- plant_nursery_views.xml (backend views)
| | -- plant_nursery_templates.xml (portal templates)
@ -220,7 +218,6 @@ The complete tree of our Odoo module therefore looks like
| | | |-- widget_a.xml
| | | |-- widget_a.xml
|-- views/
| |-- assets.xml
| |-- plant_nursery_menus.xml
| |-- plant_nursery_views.xml
| |-- plant_nursery_templates.xml