Merge pull request #167037 from schuelermine/patch-doc-submodule-default
nixos/doc/types: note submodules’ default’s behaviour
This commit is contained in:
commit
f16c8e58ca
2 changed files with 10 additions and 0 deletions
|
@ -308,6 +308,10 @@ The option set can be defined directly
|
|||
([Example: Directly defined submodule](#ex-submodule-direct)) or as reference
|
||||
([Example: Submodule defined as a reference](#ex-submodule-reference)).
|
||||
|
||||
Note that even if your submodule’s options all have a default value,
|
||||
you will still need to provide a default value (e.g. an empty attribute set)
|
||||
if you want to allow users to leave it undefined.
|
||||
|
||||
::: {#ex-submodule-direct .example}
|
||||
::: {.title}
|
||||
**Example: Directly defined submodule**
|
||||
|
|
|
@ -617,6 +617,12 @@
|
|||
(<link linkend="ex-submodule-reference">Example: Submodule defined
|
||||
as a reference</link>).
|
||||
</para>
|
||||
<para>
|
||||
Note that even if your submodule’s options all have a default
|
||||
value, you will still need to provide a default value (e.g. an
|
||||
empty attribute set) if you want to allow users to leave it
|
||||
undefined.
|
||||
</para>
|
||||
<anchor xml:id="ex-submodule-direct" />
|
||||
<para>
|
||||
<emphasis role="strong">Example: Directly defined
|
||||
|
|
Loading…
Reference in a new issue