[MGNLUI-5753] Detect un-named child UI Component creation attempt and handle accordingly Created: 23/Mar/20  Updated: 26/Mar/20  Resolved: 26/Mar/20

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

Type: Improvement Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: 1h
Time Spent: 1.25h
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by PAGES-275 Page status bar extension UI componen... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)

 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.


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