- Issue created by @rosiel
- Status changed to Closed: won't fix
7 months ago 11:35am 18 May 2024 - πΊπΈUnited States thejimbirch Cape Cod, Massachusetts
We shouldn't allow recipes to delete configuration. You'll be able to hide a field, change status to configs, but deleting is too dangerous and could bork a site.
- πΊπΈUnited States jcandan
Not re-opening, but curious if someone could chime in.
In the case of image styles, when a simple_config_update needs to swap an effect, there's no way to delete the existing effect.
- πΊπΈUnited States jcandan
Note: I am unable to just supply the full config file because I get an Error when installing a recipe that has configuration files already in the system, even if there is no difference π Error when installing a recipe that has configuration files already in the system, even if there is no difference Postponed: needs info .
- πΊπΈUnited States thejimbirch Cape Cod, Massachusetts
There are no config actions for coreβs image module yet.
simpleConfigUpdate wonβt always work on image styles as they are config entities, not simple config.
I see most recipe authors creating new image styles and configuring fields to use them. However, I can see the need for image config actions. Like adding webp to all image styles, or configuring crops or focal point.
We should open an issue against core, image module component to add config actions.
- πΊπΈUnited States jcandan
Seems something is brewing on that front.
β¨ Add a config action to remove effects from image styles Needs work