[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: |
|
||||||||
| 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: | |||||||||
| Description |
|
Timeboxed investigation 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. |