A common pattern is to have global partials that share a config. For example, a /views/partials/footer.html might be controlled in the template to use /content/partials/footer.yaml as the partial data in the template.
Normally we define how the partial editor fields work in the partials on the content. We should keep this behavior so that the editor config is still all contained in the /views/partials/ for a partial. To make this work better the editor should support referencing the partial that should be used for the editor config. Something like this:
# /content/partials/footer.yaml
$editor:
config: /views/partials/footer.html
This would allow all of the editor configurations to consistently be with the partials, but be referenced in places that are not using the partials field, such as shared configuration files.
A common pattern is to have global partials that share a config. For example, a
/views/partials/footer.htmlmight be controlled in the template to use/content/partials/footer.yamlas thepartialdata in the template.Normally we define how the partial editor fields work in the
partialson the content. We should keep this behavior so that the editor config is still all contained in the/views/partials/for a partial. To make this work better the editor should support referencing the partial that should be used for the editor config. Something like this:This would allow all of the editor configurations to consistently be with the partials, but be referenced in places that are not using the
partialsfield, such as shared configuration files.