Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-4532

New browser subapp: conditional editing

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Neutral Neutral
    • 6.0
    • None
    • None
    • None

      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.

        Acceptance criteria

              apchelintcev Aleksandr Pchelintcev
              rkovarik Roman Kovařík
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Task DoR