Odoo OWL / Web Client Coding Standards

These standards apply to the Odoo frontend: OWL components, web client services, and assets under static/. They align with Odoo’s web framework patterns and OWL best practices.

Use together with odoo-backend-standards for Python, ORM, security, and server-side XML data rules.

Module Layout & Assets

• Layout: Keep sources under static/src/ (e.g. js/, xml/ for OWL templates, optional scss/). Avoid dumping raw files into static/ without a clear bundle entry.
• Manifest: Register bundles in __manifest__.py via the assets key (current Odoo versions). Only include what the feature needs; prefer extension bundles (web.assets_backend, etc.) over duplicating entire core bundles.
• Lazy vs eager: Put rarely used UI behind lazy-loaded assets when your Odoo version supports it; keep critical path bundles lean.
• Imports: Follow project ESLint/prettier rules. Prefer @web/... public imports from the web client over deep paths into web/static/src unless maintaining core itself.

OWL Components