Refactor ApiLayoutController into 2 sub-class to support Content Templates

Created on 12 August 2025, 2 days ago

Overview

For 🌱 [META] Content templates Active we will need to make content template in the XB UI

Proposed resolution

In this issue to reduce the scope we will not support link dynamic source in the UI(follow-up issue will be made ASAP).
We will need at least πŸ“Œ Move `PropSourceEndpointTest` into new `XbConfigEntityHttpApiTest::testComponent()` Active to do this dynamice source linking.

We will refactor ApiLayoutController into ApiLayoutControllerBase, ApiLayoutController, and ApiTemplateController
So this issue will handle the GET, POST, and PATCH of the controller which should allow the UI work to be done in follow-up issue.

We will have test that prove GET, POST, and PATCH as well as publishing. The publishing in the UI will not work until we do the follow-up to handle dynamic prop sources.

The work can be started from the spike MR https://git.drupalcode.org/project/experience_builder/-/merge_requests/1415.

User interface changes

πŸ“Œ Task
Status

Active

Version

1.0

Component

Page builder

Created by

πŸ‡ΊπŸ‡ΈUnited States tedbow Ithaca, NY, USA

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