- Issue created by @phenaproxima
- π§πͺBelgium wim leers Ghent π§πͺπͺπΊ
Concerns
This restriction no longer makes sense given Drupal CMS's needs and should be lifted.
It's not that simple.
We're actively working on bringing the MVP for end-to-end
ContentTemplate
functionality to 1.0 in ~1 month: see the plan at π± [META] Content templates Active .That means any
ContentTemplate
that Drupal CMS would manually craft (that includes adapted prop sources) SHOULD be viewable/editable in that UI.However, no designs and no implementation work exists at all nor is scheduled to update the UI (JS) nor the
ComponentInstanceform
to support adapted prop sources.tl;dr: what you're asking (demanding, almost π ) would result in a crashing UI.
Suggested next steps
- Please update the issue summary with information about why those 2 adapted prop sources are "absolutely necessary". That will help frame the conversation and keep the scope reigned in π
- I was hoping to get minimal support for adapted prop sources going, in π Allow use of same-shape-adapters ahead of general adapter support in #3464003 Active , but other things have been taking priority. If you could push that forward, we might be able to achieve what you need without the above negative consequences.