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

Investigation for MGNLUI-2397 (defaultValues)

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Neutral
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.4.3
    • Component/s: None
    • Labels:
      None
    • Sprint:
      Basel 14
    • Story Points:
      8
    • Magnolia Release:
      5.4.3

      Description

      Evaluate technical options and decide on one.

      Current caveat: We merely expect form items to be JcrNewNodeAdapter to apply default values.

      • doesn't work for nodes created "upfront" (e.g. page or optional area nodes, as opposed to component nodes)
      • doesn't apply very well to non-JCR content:
        • see the dirty logic in info.magnolia.ui.form.field.factory.AbstractFieldFactory#setPropertyDataSourceAndDefaultValue
        • see info.magnolia.ui.vaadin.integration.ItemAdapter#isNew

      Possible options:

      1. Use some metadata to denote an "autogenerated" node, that has not been edited yet
      2. Compare createdDate and lastModifiedDate (careful about shortcomings)
      3. Denote at UI-framework/API level when a form/dialog should be presented as 'new'
        • as opposed to the first two options, it would not apply only to JCR

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              ejervidalo Espen Jervidalo
              Reporter:
              mgeljic Mikaël Geljić
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response: