From 250f63d8e10a03291ccf3fa0b75707be80c0bb43 Mon Sep 17 00:00:00 2001 From: gwen Date: Wed, 13 May 2026 15:02:35 +0200 Subject: [PATCH] doc: fix: nullable 09* --- docs/tutorial/nullable.rst | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/docs/tutorial/nullable.rst b/docs/tutorial/nullable.rst index d60ebd2db..77726fd81 100644 --- a/docs/tutorial/nullable.rst +++ b/docs/tutorial/nullable.rst @@ -122,7 +122,7 @@ Variables disabled when condition is null But actually, why did we want a variable to be non-mandatory? -Well, what we want is we need to be able to disable either the `port` and the `version` in case of the `address` has no value set: +Well, what we want is we need to be able to :term:`disable ` either the `port` and the `version` in case of the `address` has no value set: .. extinclude:: https://forge.cloud.silique.fr/stove/rougail-tutorials/raw/commit/v1.1_091/firefox/20-manual.yml :language: yaml @@ -179,4 +179,18 @@ Well, what we want is we need to be able to disable either the `port` and the `v variable: _.address when: null ... + +For the `disabled` property to trigger, the condition `when: null` must appear, +pointing to the `_.address` variable, that is the `socks_proxy.address` variable. + + +.. keypoints:: Key points + + We learned how to define a variable as having no value; it's possible with Rougail. + It's `default: null` and `mandatory: false`. + + We also learned to continue using type redefinition, which we learned in the previous section. + And have continued to :term:`disable ` a variable depending this on + the presence or absence of a value. +