Currently, the only way to modify an entity view or form display is by effectively calling setComponent() via the entity method exposed as a config action. This is way too limited.
How do we:
(cricket sounds)
We need a better way.
I think we should remove the setComponent action and replace it with a new, dedicated action called setDisplay or something.
I think it should be able to set multiple components at once, by name. Something like:
core.entity_view_display.taxonomy_term.tags.default:
setComponents:
name:
options:
// some component options here. Any existing ones will be overwritten.
field_something:
update: true
options:
// some component options here; these will be merged into any existing ones.
another_thing: false // remove this component entirely
Decide on whether this is a good idea, and if we think it is, implement it.
Closed: outdated
11.0
Code
We may have solved this adding in other config actions.
Yeah, all of this pretty much works already. We can close this.