[MGNLUI-5851] Customizable form field layout components Created: 04/May/20  Updated: 22/Jun/20  Resolved: 12/Jun/20

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.2

Type: Improvement Priority: Neutral
Reporter: Roman Kovařík Assignee: Roman Kovařík
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 3.35d
Original Estimate: Not Specified

Attachments: File Screen Recording.mov    
Issue Links:
Problem/Incident
causes EXTDAM-122 Remove custom UploadFieldListenerFactory Closed
dependency
depends upon MAGNOLIA-7803 Multibinding in different scopes Closed
is depended upon by LIVECOPY-184 Port of LiveCopyAwareFormDialogPresen... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Epic Link: Migrate apps to new UI framework
Sprint: UI FW 2, UI FW 3, UI FW 4
Story Points: 5

 Description   

Expected results

I can add custom components to all forms fields.

Workaround

I can achieve this only by providing custom factory implementations for all fields.



 Comments   
Comment by Roman Kovařík [ 12/Jun/20 ]

From original description:

Development notes

PoC implements type mapping for the field layout which can be redefined like this:

<components>
 <id>app-pages-app-detail</id>
 <type-mapping>
 <type>info.magnolia.ui.vaadin.form.field.FieldLayout</type>
 <implementation>info.magnolia.livecopy.app.ui.vaadin.form.field.LiveCopyFieldLayout</implementation>
 </type-mapping>
</components>

 Disadvantage of this approach is inability to decorate the field layout form multiple submodules.

 At least the custom implementation can be scope to an app/subapp.

Generated at Mon Feb 12 09:30:41 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.