[MGNLUI-4553] Finalize JCR property set implementation Created: 11/May/18  Updated: 17/Sep/18  Resolved: 17/Sep/18

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

Type: Task Priority: Neutral
Reporter: Antti Hietala Assignee: Aleksandr Pchelintcev
Resolution: Done Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLUI-4529 Add support for JCR properties in con... Closed
is depended upon by MGNLUI-4532 New browser subapp: conditional editing Closed
is depended upon by MGNLUI-4554 Implement Vaadin 8 - based inline row... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: UI framework: forms, dialogs, content editing
Sprint: Basel 153, Basel 154, Basel 155, Basel 156
Story Points: 13

 Description   

Acceptance criteria:

  • automatic/default conversion support: JCR values should be effortlessly convertible to the expected field/column definition types (via BeanUtils converter functionality).
  • untie PropertySet implementation from field/column definition - instead a dry and simple property definition should be used: id and type should be enough.
  • get rid of the alternative JcrPropertySet implementation: there are currently two of them, only JcrNodePropertySet needs to remain.
  • fix the synchronisation issues between the Grid and the JcrNodePropertySet: not necessarily the issue of a property set component itself
  • support for editing JCR properties.
    • generalise relevant components so that properties can be displayed and edited in the Grid/TreeGrid.
    • split JcrItemPropertySet functionality-wise (provide implementation for the Nodes and Properties separately).
    • introduce an interface (and impl) for the renamable properties.

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