From cc14bb8b76ffe694bffbba7066f59a6b8358f6f6 Mon Sep 17 00:00:00 2001 From: Mathias Brodala Date: Fri, 28 Jun 2024 09:42:52 +0200 Subject: [PATCH] Annotate TCA options in "none" docs --- Documentation/ColumnsConfig/Type/None/Index.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/Documentation/ColumnsConfig/Type/None/Index.rst b/Documentation/ColumnsConfig/Type/None/Index.rst index c0011edd4..1e357df33 100644 --- a/Documentation/ColumnsConfig/Type/None/Index.rst +++ b/Documentation/ColumnsConfig/Type/None/Index.rst @@ -15,13 +15,13 @@ These are the :ref:`none type `, the :ref:`passthrough type ` discards values send for type none and never +* The :ref:`DataHandler ` discards values send for type `none` and never persists or updates them in the database. -* Type none is the only type that does **not** necessarily need a database field. -* Type none fields does have a default renderType in FormEngine that displays the value as readonly +* Type `none` is the only type that does **not** necessarily need a database field. +* Type `none` fields does have a default `renderType` in FormEngine that displays the value as readonly if a database field exists and the value can be formatted. -* If no database field exists for none fields, an empty readonly input field is rendered by default. -* Type none fields are designed to be not rendered at other places in the backend, for instance they can +* If no database field exists for `none` fields, an empty readonly input field is rendered by default. +* Type `none` fields are designed to be not rendered at other places in the backend, for instance they can not be selected to be displayed in the list module "single table view" if everything has been configured correctly.