[MGNLFE-25] 'Page' in FE libraries instantiates mapped component Created: 19/Feb/20 Updated: 24/Nov/20 Resolved: 24/Nov/20 |
|
| Status: | Closed |
| Project: | Magnolia Frontend Helpers |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| 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)
|
||||||||
| Release notes required: |
Yes
|
||||||||
| Documentation update required: |
Yes
|
||||||||
| Date of First Response: | |||||||||
| Epic Link: | SPA Editor Backlog | ||||||||
| Description |
|
As a developer when I use a Page component (or directive) in my FE app, I want Magnolia libraries to automatically instantiate the FE component which is mapped to the templateDefinition cooresponding to a specified 'path', with a default of using the current path in the url. TODO: pm provides more details. |
| Comments |
| Comment by Robert Šiška [ 24/Nov/20 ] |
|
czimmermann Not sure I understand correctly, but this seems to be working. You only pass template annotations and the page content to EditablePage and it instantiates correct component based page template and mappings. Can we close this? |
| Comment by Christopher Zimmermann [ 24/Nov/20 ] |
|
This was implemented long ago - probably under another ticket. Closing as outdated. |