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
📌 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...
None see follow-up ✨ Allow linking a component prop of a template to a dynamic field Active
Postponed
1.0
… to be triaged
changing because 📌 Refactor ApiLayoutController into 2 sub-class to support Content Templates Active change to not split ApiLayoutController into 2 classes. We may need do that in this issue be we shall see.
