[MGNLREST-777] Add support for nested reference Resolver Created: 06/Dec/23 Updated: 07/Dec/23 Resolved: 07/Dec/23 |
|
| Status: | Closed |
| Project: | Magnolia REST Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Rishab Dhar | Assignee: | Unassigned |
| Resolution: | Not an issue | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Epic Link: | Multiple Pages App LD | ||||||||
| Team: | |||||||||
| Work Started: | |||||||||
| Description |
|
Currently the rest module supports jcrReferenceResolver and the assetReferenceResolver, however in fragments use case in The normal jcrReferenceResolver can resolve references to the banner workspace but cannot resolve deeply nested references within the page. The assetReference resolver resolves references only to the properties defined for the main pages app. So neither of them are currently capable for this use case. |