Skip to content

Draft: #3518248 Spike "Template Layout controller"

Ted Bowmanrequested to merge
issue/experience_builder-3518248:3518248-layout-controller into 1.x

This MR is spike to support the related front-end spike !1406 (closed)

EDIT: brought in changes from !1406 (closed) to here.

The current UI code is a little messy for velocity purposes and since this is a spike. Code clean up will come later.

Backend:

This MR moves most of the logic form ApiLayoutController into ApiLayoutControllerBase. ApiLayoutController will continue to be used for content entities that have the ComponentTree field. I leaving name the of the controller the same to make the diff smaller for now. Added a new ApiTemplateLayoutController extends ApiLayoutControllerBase which will handle ContentTemplate entities.

For now I have test coverage in ApiTemplateLayoutControllerTest the test proves that GET, POST, PATCH work for the new controller. It also proves the template is added to the auto-save and it can be published.

There are few other changes to auto-save logic to not assume that all entities in auto-save already have saved version.

Closes #3518248

Edited by Ted Bowman

Merge request reports