#86803Possibility to import other yaml files into a yaml site configuration
Description
Having multi domain instances with same plugins (e.g. news, events etc.) located inside each instance it is currently neccessary to write down the same site configuration (here especially: route enhancers) for each domain. It would be really a nice feature to add the possibility to include / import other yaml (partial) configurations into a yaml site configuration file. Like ckeditor rte configuration does by…
imports:
- { resource: "EXT:rte_ckeditor/Configuration/RTE/Processing.yaml" }
- { resource: "EXT:rte_ckeditor/Configuration/RTE/Editor/Base.yaml" }
- { resource: "EXT:rte_ckeditor/Configuration/RTE/Editor/Plugins.yaml" }
…the same might be possible for site configurations:
imports:
- { resource: "typo3conf/sites/global/route-enhancers-news.yaml" }
- { resource: "typo3conf/sites/gloabl/route-enhancers-events.yaml" }
And the referenced files might contain some partial configuration like:
routeEnhancers:
NewsPlugin:
type: Extbase
limitToPages: [182,190,211,309] <- here all news detailpids inside a multidomain environment could be set
extension: Extension
plugin: News
routes:
- { routePath: '/{news_title}', _controller: 'News::show', _arguments: {'news_title': 'news'} }
defaultController: 'News::show'
aspects:
news_title:
type: PersistedAliasMapper
tableName: 'tx_ext_domain_model_news'
routeFieldName: 'title'