For clarity, some data files are formatted as pseudo-tree structure. This is somewhat confusing and dangerous when the structure has no meaning... so add meaning: * allow nesting menuitems, nested items are set as children to the parent they're nested in * update schema to allow an icon *or* a parent on regular menu items, and neither on nested (they have an implicit parent meaning can't have an icon) * remove attributes which don't actually exist from the menuitem schema * also type sequence as an integer while at it Convert two large-ish menuitem data files to recursive form. closes odoo/odoo#54564 Related: odoo/enterprise#11887 Signed-off-by: Xavier Morel (xmo) <xmo@odoo.com>
32 lines
810 B
XML
32 lines
810 B
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<odoo>
|
|
<menuitem id="menu_mrp_root"
|
|
name="Manufacturing"
|
|
groups="group_mrp_user,group_mrp_manager"
|
|
web_icon="mrp,static/description/icon.png"
|
|
sequence="35">
|
|
|
|
<menuitem id="menu_mrp_manufacturing"
|
|
name="Operations"
|
|
sequence="10"/>
|
|
|
|
<menuitem id="mrp_planning_menu_root"
|
|
name="Planning"
|
|
sequence="15"/>
|
|
|
|
<menuitem id="menu_mrp_bom"
|
|
name="Products"
|
|
sequence="20"/>
|
|
|
|
<menuitem id="menu_mrp_reporting"
|
|
name="Reporting"
|
|
sequence="25"/>
|
|
|
|
<menuitem id="menu_mrp_configuration"
|
|
name="Configuration"
|
|
groups="group_mrp_manager"
|
|
sequence="100"/>
|
|
|
|
</menuitem>
|
|
</odoo>
|