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

Detect un-named child UI Component creation attempt and handle accordingly

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Done
    • Neutral
    • 6.2
    • None
    • None
    • None

    Description

      Currently info.magnolia.ui.UIComponent#create(java.lang.Class, java.lang.Object...) doesn't check whether the instance we're creating is a UI component.

      In order to make the underlying mechanism more robust, we can/should detect that and delegate the call to the child UI component creation flow: init a bean storage, context reference etc.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                apchelintcev Aleksandr Pchelintcev
                apchelintcev Aleksandr Pchelintcev
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Task DoD

                    Time Tracking

                      Estimated:
                      Original Estimate - Not Specified
                      Not Specified
                      Remaining:
                      Time Spent - 1.25h Remaining Estimate - 1h
                      1h
                      Logged:
                      Time Spent - 1.25h Remaining Estimate - 1h
                      1.25h