From 7696f6e6f31d9ddcc170fea2ccf1dbcdaae057fd Mon Sep 17 00:00:00 2001 From: Zynth-dev <44590222+Zynth-dev@users.noreply.github.com> Date: Wed, 13 Mar 2024 21:16:09 +0100 Subject: [PATCH] Update index.rst to provide missing information on the on_value behavior (#3652) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * Update index.rst to provide missing information on the on_value behavior The on_value behavior was unclear about what happens when the selected-value is set to the same value as it already was. * Update components/select/index.rst Co-authored-by: guillempages --------- Co-authored-by: guillempages Co-authored-by: H. Árkosi Róbert --- components/select/index.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/components/select/index.rst b/components/select/index.rst index 756964340..a79c4d926 100644 --- a/components/select/index.rst +++ b/components/select/index.rst @@ -70,7 +70,7 @@ For more information on using lambdas with select, see :ref:`select-lambda_calls ``on_value`` ************ -This automation will be triggered when a new value is published. In :ref:`Lambdas ` +This automation will be triggered whenever a value is set/published, even if the value is the same as before. In :ref:`Lambdas ` you can get the value from the trigger with ``x`` and the index offset of the selected value with ``i``. .. code-block:: yaml