danvics/ytdl-sub
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(config): Clarify preset ordering priority

Browse source 
Refs #1276
This commit is contained in:
Ross Patterson 2025-08-17 08:20:33 -07:00
parent 3c45e2217e
commit 402106559e
No known key found for this signature in database
GPG key ID: 2EFF7CCE6828E359
1 changed files with 13 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
docs/source/config_reference/config_yaml.rst
View file

@ -82,9 +82,18 @@ Presets also support inheritance from multiple presets:
- "custom_preset" - "custom_preset"
- "parent_preset" - "parent_preset"
In this example, ``child_preset`` will inherit all fields from ``custom_preset`` In this example, ``child_preset`` will inherit all fields from ``custom_preset`` and
and ``parent_preset`` in that order. The bottom-most preset has the highest ``parent_preset`` in that order. The bottom-most preset has the highest priority. More
priority. specifically, presets are merged using `mergedeep`_ via `a TYPESAFE_ADDITIVE merge`_,
which means:
- if two conflicting keys arent lists or mappings, overwrite the higher priority one
- otherwise, combine then re-evaluate
If you are only inheriting from one preset, the syntax ``preset: "parent_preset"`` is If you are only inheriting from one preset, the syntax ``preset: "parent_preset"`` is
valid YAML. Inheriting from multiple presets require use of a list. valid YAML. Inheriting from multiple presets require use of a list.
.. _`mergedeep`:
https://mergedeep.readthedocs.io/en/latest/
.. _`a TYPESAFE_ADDITIVE merge`:
https://mergedeep.readthedocs.io/en/latest/index.html#merge-strategies