[MGNLREST-211] Produce page-editor-hints Created: 16/May/19 Updated: 18/Nov/19 Resolved: 05/Nov/19 |
|
| Status: | Closed |
| Project: | Magnolia REST Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | Assignee: | Robert Šiška |
| 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)
|
||||||||
| Release notes required: |
Yes
|
||||||||
| Documentation update required: |
Yes
|
||||||||
| Date of First Response: | |||||||||
| Epic Link: | SPA Editor | ||||||||
| Sprint: | SPA Editor 7, SPA Editor 8, SPA Editor 9 | ||||||||
| Story Points: | 5 | ||||||||
| Description |
|
User story: Notes: Acceptance criteria:
Suggestion: Example page-editor-comment for an area: <!-- cms:area content="website:/travel/about" name="navigation" availableComponents="" type="noComponent" label="Navigation" inherit="false" optional="false" created="false" createdAreaNode="false" showAddButton="false" showNewComponentArea="false" activationStatus="2" --> |
| Comments |
| Comment by Bartosz Staryga [ 04/Jul/19 ] |
|
It would be nice if existed delivery API was extended with the relevant comment, eg: "main": { ... "@name": "main", "mgnl:editorHints": { "before": "<!-- cms:area ... -->", "after": "<!-- /cms:area -->" } ... }
|