[MGNLUI-4532] New browser subapp: conditional editing Created: 02/Aug/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: Roman Kovařík Assignee: Aleksandr Pchelintcev
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File editable-vs-not-editable.png    
Issue Links:
dependency
depends upon MGNLUI-4553 Finalize JCR property set implementation Closed
is depended upon by MGNLUI-4531 Polish browsing functionality impleme... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: UI framework implementation
Sprint: Basel 155, Basel 156
Story Points: 3

 Description   

Current configuration app has some noneditable field for nodes, editable for properties ("value" of property)

Some research hints:

  • the case is the most relevant to the TreeGrid: there we might display both properties and nodes, but only properties can have a value and => only for the case of properties the cells of the corresponding column can/should be editable.
  • the workaround above suggests to block the whole row from being edited depending on the data. But in our case it might only certain cells, not the whole row that should be non-editable, so most likely the workaround is not applicable to us.
  • however, we should maybe research whether we could columns not just to the component that is configured in the definition, but to a special wrapper which would present a said component once the cells is clearly editable (the underlying row is bound to Node) and smth readonly (e.g. a label) - if not.

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