Issue Feature Closed

#106858Split settings.definition.yaml

Steffen Matthes 06/10/25, 09:29 updated 01/26/26, 16:55

Description

I would like to split the settings.definition.yaml into different yaml files in a site set to achieve a better overview, comparable to the integration of `*.typoscript` or `*.tsconfig` files.
For TYPO3 v13.4.13 I don’t see an option yet. I would love it if this could be done with TYPO3 v14.x.

Reviews 1

History 67

  1. Chris Müller changed subject settings.deffinition.yaml splitten Split settings.definition.yaml <span data-processor="relativetime" data-value="2025-06-10T17:01:09+00:00" > 06/10/25, 17:01 </span>

  2. Eric Harrer commented <span data-processor="relativetime" data-value="2026-01-26T16:24:10+00:00" > 01/26/26, 16:24 </span>

    Andreas Kießling wrote in #note-2:
    > Do yaml imports work?
    >
    > https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/Routing/Examples.html#routing-examples-imports
    >
    > If used that for my csp config as well with relative paths

    No, YAML imports do not work and are expressly not allowed.
    See discussion here: https://review.typo3.org/c/Packages/TYPO3.CMS/+/92516

  3. Eric Harrer commented <span data-processor="relativetime" data-value="2026-01-26T16:54:11+00:00" > 01/26/26, 16:54 </span>

    The discussion in the associated patch review has shown that YAML imports in settings.definitions.yaml are deliberately not provided in order to keep site sets strictly self-contained and avoid unwanted dependencies.

    The original goal of better structuring large settings files can already be achieved today by dividing them into multiple site sets with sub-dependencies. This approach is conceptually clean and offers additional advantages in UI structuring.

    In my opinion, this issue has been sufficiently clarified and can be closed.

  4. Garvin Hicking commented and changed status Under Review Closed <span data-processor="relativetime" data-value="2026-01-26T16:55:12+00:00" > 01/26/26, 16:55 </span>

    Closed and solved via (from the patch discussion):

    Yes, subdependencies within site sets seem to be a useful approach for splitting up large setting definitions. Thanks for the food for thought!