Refactor(or attempt to) all or most ApiLayoutController*Test classes to also test ContentTemplate entities

Created on 29 August 2025, about 1 month ago

Overview

In πŸ“Œ Refactor ApiLayoutController into 2 sub-class to support Content Templates Active we refactored to ApiLayoutController to also handle ContentTemplates. Here we did the bare minimum to unblock the front-end, to work on ✨ Render template and support component operations in preview canvas Active

In #3541021 we add minimal test coverage because it probably makes sense to look all ApiLayoutController*Test classes and see if it makes sense to use data providers to test both content entities and templates. It may not in many cases but it is probably worth looking at before we create a bunch of duplicated test functions.

Proposed resolution

After πŸ“Œ Refactor ApiLayoutController into 2 sub-class to support Content Templates Active or actually probably after πŸ“Œ [PP-2] Accept Dynamic Props in ApiTemplateLayoutController for content templates Postponed also because the functionality would be more complete, refactor ApiLayoutController*Test classes where it makes sense to handle both content entities and content templates

User interface changes

πŸ“Œ Task
Status

Active

Version

1.0

Component

Internal HTTP API

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