[MGNLREST-119] Research solution for resolving result of a list of reference nodes Created: 29/Sep/17  Updated: 25/Jan/18  Resolved: 22/Jan/18

Status: Closed
Project: Magnolia REST Framework
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Sang Ngo Huu Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLREST-160 Implement: Moving reference resolver ... Closed
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)
Date of First Response:
Epic Link: REST Phase2
Sprint: Saigon 129, Saigon 130, Saigon 131
Story Points: 5

 Description   

For the case reference property is array of uuids or paths
propertyName=[cafe-babe-cafebabeee,anot-her-uuid] we need to resolve it as a list of nodes, but with NodeWrapper/Decorator, there is no array/list supported. Currently, resolved nodes is wrapped as children nodes in a ReadOnlyNode, but need to find better solution.



 Comments   
Comment by Sang Ngo Huu [ 12/Dec/17 ]

MNGLREST-160 might fix this issue

Comment by Mikaël Geljić [ 22/Jan/18 ]

Resolved by passing UUID as strings to ReferenceResolver.
Then from usage point in (NodeWriter, invoke resolver for single or multi-value property, with appropriate JsonGenerator calls (startArray vs. write property).

Generated at Mon Feb 12 06:56:47 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.