Julien Mougenot
3e3dce0eb8
Rationale: The majority of cases where an ir.asset is manually declared outside of manifest files is to specifically add a single asset file. This means developers are specifying a single asset *path*, and not a glob expression. In this context, it seems better to name the filepath field `path`, and document that it can be specified with a glob expression when (seldom) needed, rather than making the exception appear to be the norm - possibly puzzling many developers (What's a glob and why do I need one?) The doc is updated as well, and some spell-checking and wording improvements were done too. This required some adaptations to the existing `ir.asset` declarations: - odoo/enterprise#17465 - odoo/design-themes#459 closes odoo/odoo#68695 Related: odoo/upgrade#2348 Signed-off-by: Olivier Dony (odo) <odo@openerp.com>
20 lines
628 B
XML
20 lines
628 B
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<odoo>
|
|
|
|
<template id="s_title" name="Title">
|
|
<section class="s_title pt40 pb40" data-vcss="001">
|
|
<div class="container s_allow_columns">
|
|
<h1 style="text-align: center;"><font style="font-size: 62px;">Your Site Title</font></h1>
|
|
</div>
|
|
</section>
|
|
</template>
|
|
|
|
<record id="website.s_title_000_scss" model="ir.asset">
|
|
<field name="name">Title 000 SCSS</field>
|
|
<field name="bundle">web.assets_frontend</field>
|
|
<field name="path">website/static/src/snippets/s_title/000.scss</field>
|
|
<field name="active" eval="False"/>
|
|
</record>
|
|
|
|
</odoo>
|