As I work on the SEO recipe for Drupal CMS, I am creating config actions that create a field, then add it to all the content types of a site.
When I use the setComponent(s) config action, placing the field instance in the entity_form_display, I need to define settings.render_theme.
config:
actions:
core.entity_form_display.node.*.default:
setComponents:
-
name: field_seo_analysis
options:
type: yoast_seo_widget
weight: 18
region: content
settings:
render_theme: olivero
render_view_mode: default
edit_title: 0
edit_description: 0
third_party_settings: { }
If I leave it null, which is allowed, the form selects the first theme alphabetically, which in a default install is Claro.
We had a similar situation come up creating a config action to place blocks. As recipe creators we don't necessarily know the name of the them the recipe is going to be applied to. But what we do know is that there is a set Default theme and a set Admin theme.
That action is documented here:
https://git.drupalcode.org/project/distributions_recipes/-/blob/1.0.x/do...
This is definitely a low priority feature request, but I wanted to capture it to see if it would be possible. It would make configuring this module in recipes all the more safer.
Thanks!
Active
2.0
Code
Sounds like a useful addition.
We'd have to add some special values to the widget configuration and make sure those can never be valid theme names. That could be something like reserved:default and reserved:admin since I believe a colon can not be in the theme system name.