Upon applying a recipe, XB should reapply config actions that target component entities

Created on 10 July 2025, 17 days ago

Overview

XB has a strange relationship with config actions, because you cannot effectively run config actions against component recipes?

Why? Because, unless you ship component entities in the recipe's config directory, the component entities won't exist until after config actions have run. (They are created just before content is imported, by XB's RecipeSubscriber.)

The net result here is that config actions which target XB component entities will silently fail to do anything, and it looks for all the world like a crazy bug.

Proposed resolution

RecipeSubscriber should, upon the application of the recipe, reapply all config actions that target any experience_builder.component.* entities. It's surprisingly simple to do -- the subscriber can simply take the config action plugin manager as an argument, and call its applyAction() method.

This will make component-targeted config actions work the same ways as any other config actions.

User interface changes

None.

πŸ› Bug report
Status

Active

Version

0.0

Component

… to be triaged

Created by

πŸ‡ΊπŸ‡ΈUnited States phenaproxima Massachusetts

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024