Overview

While working on #3582478: Symmetrically translatable config-defined component trees, STEP 2: change config schema type for `inputs` to allow translating via core's Config Translation UI for ContentTemplates & PageRegions, I ended up needing to investigate where and whether there are differences between the 3 Canvas config entity types storing component trees.

This was made more difficult to assess because the same logic was duplicated in three places.

Proposed resolution

Remove the duplication; move as much out of ContentTemplate|PageRegion|Pattern into ComponentTreeConfigEntityBase as possible.

User interface changes

None.

Issue fork canvas-3586216

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

wim leers created an issue. See original summary.

wim leers’s picture

Assigned: wim leers » Unassigned
Status: Active » Needs review
Issue tags: +blocker
penyaskito’s picture

Status: Needs review » Needs work

I'd feel better knowing what's the reason for the different order of calls predating this refactor.

wim leers’s picture

Title: Follow-up for #3545236: move triplicated logic into `ComponentTreeConfigEntityBase` » Follow-up for #3545236: move triplicated logic into `ComponentTreeConfigEntityBase` to simplify future update paths targeting component trees
wim leers’s picture

Status: Needs review » Reviewed & tested by the community

Thanks, @penyaskito!

  • wim leers committed 48f7e312 on 1.x
    chore(Config management): #3586216 Follow-up for #3545236: move...
wim leers’s picture

Status: Reviewed & tested by the community » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.