[MGNLREST-380] Implement NorsuRichTextLinkResolver Created: 07/May/22 Updated: 26/Sep/22 Resolved: 21/Sep/22 |
|
| Status: | Closed |
| Project: | Magnolia REST Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.0.0 |
| Type: | Story | Priority: | Neutral |
| Reporter: | Oanh Thai Hoang | Assignee: | Rishab Dhar |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | 3h | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Attachments: |
|
||||||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Sub-Tasks: |
|
||||||||||||||||||||||||||||
| Template: |
|
||||||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||||||||||
| Task DoD: |
[X]*
Doc/release notes changes? Comment present?
[X]*
Downstream builds green?
[X]*
Solution information and context easily available?
[X]*
Tests
[X]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||
| Epic Link: | Norsu delivery endpoint (phase 1) | ||||||||||||||||||||||||||||
| Sprint: | DevX 18, DevX 19 | ||||||||||||||||||||||||||||
| Story Points: | 5 | ||||||||||||||||||||||||||||
| Team: | |||||||||||||||||||||||||||||
| Description |
|
Docu about how JCR reference The norsu rich text reference resolver will not rely on RichTextLinkResolver the same way like resolve by uuid and workspace. We can reuse by hash, id or even path Note:
Example use case inspired from Topher: As an author, on a landing page for New Years, I want to have a paragraph that links to 3 different sub-pages which each have a different party idea. I want to link to an asset which is a PDF with pary invitations. |
| Comments |
| Comment by Oanh Thai Hoang [ 21/Jul/22 ] |
|
Here is example of rich text has linked to jcr page and jcr dam Here is current data of above rich text field without resolver: "foo": "<p>page: <a href=\"${link:{uuid:{00217a00-6806-4f85-8f76-c10622e8c562},repository:{website},path:{/test}}}\">title</a></p>\n\n<p> </p>\n\n<p>asset: <a href=\"${link:{uuid:{8a58b107-fcdb-4832-b6a7-a28290cb1a6a},repository:{dam},path:{/samples/stravinsky.jpg}}}\">stravinsky</a></p>\n" |
| Comment by Christopher Zimmermann [ 08/Sep/22 ] |
|
Links should be relative links with no context. This is best for frontend developers. |