[MGNLREST-201] Get templateDefinitions from OOTB REST endpoint Created: 01/Apr/19 Updated: 06/Aug/19 Resolved: 06/Aug/19 |
|
| Status: | Closed |
| Project: | Magnolia REST Framework |
| Component/s: | None |
| Affects Version/s: | 2.1.1 |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | Assignee: | Unassigned |
| Resolution: | Obsolete | 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)
|
||||||||
| Epic Link: | SPA Editor | ||||||||
| Description |
|
Note: This ticket https://jira.magnolia-cms.com/browse/PAGES-180 probably makes this ticket obsolete. Need to review further. User story:
Notes: In order for a SPA to correctly generate the page editor hints (HTML comments), which include lists of which components are available in each area, it needs to have the template definitions. (Currently this is achieved with at a template and javascript model which access the templateRegistry). Acceptance criteria:
|
| Comments |
| Comment by Christopher Zimmermann [ 06/Aug/19 ] |
|
Not needed at present because another ticket more directly solves the use case: |