- Merge request !107Resolve #3547598 "Better dynamic prop source suggestions" → (Merged) created by wim leers
- Merge request !129Resolve #3547598 "Formdisplay getcomponents is absurdly bad" → (Merged) created by wim leers
📌
Move `PropSourceEndpointTest` into new `XbConfigEntityHttpApiTest::testComponent()`
Active
built a HTTP API on top of FieldForComponentSuggester.
That's been around for >1 year and never used in the UI. So the labels are developer-supporting, not end-user supporting. But confusing.
This Article's Title → just Title
Subset of this Article's field_silly_image: alt (1 of 7 props — absent: entity, title, width, height, srcset_candidate_uri_template, src_with_alternate_widths) switch to a nested structure: just {Silly Image: {Alternative Text}, to allow for a nested contextual menu to be presented in the UI being added at
✨
Allow linking a component prop of a template to a dynamic field
Active
.
Subset of this Article's field_silly_image: src_with_alternate_widths, alt, width, height (4 of 7 props — absent: entity, title, srcset_candidate_uri_template) → switch to just Silly Image
See above!
✨ Allow linking a component prop of a template to a dynamic field Active becomes much better 😊
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.