Create a centralized service to handle loading component trees

Created on 3 April 2025, 3 months ago

Overview

As part of supporting content type templates, we need to abstract the storage of component trees. One problem facing us is that component tree loading is currently a tangle of if/elseif/else structures that gets repeated multiple times in XB's codebase.

Proposed resolution

Move that logic to a single centralized ComponentTreeLoader service, which will allow us to further refactor and refine the way component trees are loaded from storage.

User interface changes

None should result from this change.

🐛 Bug report
Status

Active

Version

0.0

Component

Internal HTTP API

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