Contrib.social

[PP-2] Accept Dynamic Props in ApiTemplateLayoutController for content templates

Open on Drupal.org →
Created on 13 August 2025, 6 months ago

Overview

Follow-up to 📌 Refactor ApiLayoutController into 2 sub-class to support Content Templates Active
Obviously content templates should have at least 1 dynamic prop
That requirement was taken out in 📌 Refactor ApiLayoutController into 2 sub-class to support Content Templates Active to allow a better scoped issue and to allow ✨ Render template and support component operations in preview canvas Active to be a smaller scope

In this issue we should add ability for ApiTemplateLayoutController to accept component with dynamic props.

The issue is currently blocked by 📌 ComponentSourceInterface::inputToClientModel needs to support passing an entity Active

This issue will not handle the UI parts. That will be handled by ✨ Allow linking a component prop of a template to a dynamic field Active which is blocked by this issue

Proposed resolution

📌 ComponentSourceInterface::inputToClientModel needs to support passing an entity Active it may just be matter adding test coverage that ApiTemplateLayoutController can accept dynamic props and these can be published. You can see test coverage from the original research spike, which contained a hack fix for #3513590, here https://git.drupalcode.org/project/experience_builder/-/merge_requests/1...

User interface changes

None see follow-up ✨ Allow linking a component prop of a template to a dynamic field Active

📌 Task
Status

Postponed

Version

1.0

Component

… to be triaged

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

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024