From 2b75fb4bbb6ac544c19ceba799e4cdc448d39d13 Mon Sep 17 00:00:00 2001 From: Victor Feyens Date: Mon, 21 Nov 2022 16:23:49 +0000 Subject: [PATCH] [FIX] developer/*: consistent code-block language specification X-original-commit: 387cf15e7f0abde7fcc6ae29d362d04667ac60d8 Part-of: odoo/documentation#3029 --- .../odoo_sh/getting_started/first_module.rst | 2 +- content/developer/howtos/accounting_localization.rst | 4 ++-- content/developer/reference/backend/testing.rst | 2 +- content/developer/reference/frontend/assets.rst | 2 +- .../reference/frontend/framework_overview.rst | 2 +- content/developer/reference/frontend/registries.rst | 12 ++++++------ content/developer/reference/frontend/services.rst | 4 ++-- 7 files changed, 14 insertions(+), 14 deletions(-) diff --git a/content/administration/odoo_sh/getting_started/first_module.rst b/content/administration/odoo_sh/getting_started/first_module.rst index 848c2ddcf..f825a1464 100644 --- a/content/administration/odoo_sh/getting_started/first_module.rst +++ b/content/administration/odoo_sh/getting_started/first_module.rst @@ -141,7 +141,7 @@ Uncomment the content of the files: the manifest of your module, including for instance its title, description and data files to load. You just need to uncomment the access control list data file: - .. code-block:: xml + .. code-block:: python # 'security/ir.model.access.csv', diff --git a/content/developer/howtos/accounting_localization.rst b/content/developer/howtos/accounting_localization.rst index fa37e8320..41a957af1 100644 --- a/content/developer/howtos/accounting_localization.rst +++ b/content/developer/howtos/accounting_localization.rst @@ -23,7 +23,7 @@ Building a localization module The structure of a basic ``l10n_XX`` module may be described with the following :file:`__manifest__.py` file: -.. code-block:: py +.. code-block:: python { "name": "COUNTRY - Accounting", @@ -345,7 +345,7 @@ Accounting reports should be added via a separate module `l10n_XX_reports` that Basic :file:`__manifest__.py` file for such a module looks as following: -.. code-block:: py +.. code-block:: python { "name": "COUNTRY - Accounting Reports", diff --git a/content/developer/reference/backend/testing.rst b/content/developer/reference/backend/testing.rst index 7c685378e..ccdfe2bea 100644 --- a/content/developer/reference/backend/testing.rst +++ b/content/developer/reference/backend/testing.rst @@ -199,7 +199,7 @@ Besides tags you can also specify specific modules, classes or functions to test. The full syntax of the format accepted by :option:`--test-tags ` is: -.. code-block:: +.. code-block:: text [-][tag][/module][:class][.method] diff --git a/content/developer/reference/frontend/assets.rst b/content/developer/reference/frontend/assets.rst index cedce9ed9..1ed250f05 100644 --- a/content/developer/reference/frontend/assets.rst +++ b/content/developer/reference/frontend/assets.rst @@ -63,7 +63,7 @@ with a dedicated `assets` key which contains a dictionary. The dictionary maps bundle names (keys) to the list of files they contain (values). It looks like this: -.. code-block:: py +.. code-block:: python 'assets': { 'web.assets_backend': [ diff --git a/content/developer/reference/frontend/framework_overview.rst b/content/developer/reference/frontend/framework_overview.rst index 8395d52ce..492476662 100644 --- a/content/developer/reference/frontend/framework_overview.rst +++ b/content/developer/reference/frontend/framework_overview.rst @@ -328,7 +328,7 @@ browser. Example: -.. code-block:: js +.. code-block:: javascript import { evaluateExpr } from "@web/core/py_js/py"; diff --git a/content/developer/reference/frontend/registries.rst b/content/developer/reference/frontend/registries.rst index 4a3e3a1c7..834691a39 100644 --- a/content/developer/reference/frontend/registries.rst +++ b/content/developer/reference/frontend/registries.rst @@ -161,11 +161,11 @@ direct child. This component is basically a live representation of the ordered list of components registered in the main components registry. API - .. code-block:: + .. code-block:: text interface { - Component: Owl Component class - props?: any + Component: Owl Component class + props?: any } @@ -243,7 +243,7 @@ with the following three keys: For example: -.. code-block:: js +.. code-block:: javascript import { registry } from "@web/core/registry"; @@ -258,7 +258,7 @@ For example: The systray registry is an ordered registry (with the `sequence` number): -.. code-block:: js +.. code-block:: javascript const item = { Component: MySystrayItem @@ -291,7 +291,7 @@ The user menu calls all the functions defining items every time it is opened. Example: -.. code-block:: js +.. code-block:: javascript import { registry } from "@web/core/registry"; diff --git a/content/developer/reference/frontend/services.rst b/content/developer/reference/frontend/services.rst index 8f3c63266..e92069efb 100644 --- a/content/developer/reference/frontend/services.rst +++ b/content/developer/reference/frontend/services.rst @@ -902,7 +902,7 @@ API remove the value with the given key from the :ref:`user context` - .. code-block:: js + .. code-block:: javascript userService.removeFromContext("isFriend") @@ -914,6 +914,6 @@ API check if the user is part of a group - .. code-block:: js + .. code-block:: javascript const isInSalesGroup = await userService.hasGroup("sale.group_sales")