[MGNLFE-182] Discovery - Component Autogeneration should work in SPA Editor Created: 16/Mar/22  Updated: 05/Apr/22  Resolved: 28/Mar/22

Status: Closed
Project: Magnolia Frontend Helpers
Component/s: None
Affects Version/s: 1.0.5
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones PAGES-1128 Component Autogeneration should work ... 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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Epic Link: SPA Editor Backlog
Sprint: DevX 6
Story Points: 3
Team: DeveloperX

 Description   

Timeboxed investigation
Goal of investigation is to determine possible implementations and how long they would be expected to take.


Magnolia's component autogeneration functionality allows page areas to be populated with required components. See: https://documentation.magnolia-cms.com/display/DOCS62/Component+autogeneration

In an FTL-rendered site the configured components are created by AreaElement but nothing happens in an MGNLFE site.



 Comments   
Comment by Christopher Zimmermann [ 28/Mar/22 ]

Closing this discovery ticket. We'll do the discovery on the main ticket - linked.

Generated at Mon Feb 12 05:45:02 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.