Expected Behavior

References in resolved relations are resolved as it is defined in the API request by parameter "resolved_relations".
We expected the same behaviour than in the deprecated SDK where the resolved relations themselves get "enriched".

Current Behavior

When some resolved relation does have a reference on its own. This reference is not resolved, although the data is returned from the API response.

Steps to Reproduce

Given relations:
"A" has a reference to "B" and "B" has a reference to "C".

"resolved relations" in the API Request:

"resolved_relations=A.B,B.C"

API response:

"uuid": "<uuid of A>"
"content": {
    "B": "<uuid of B>"
 }
"rels": [
  {
    "uuid": "<uuid of B>"
    "content": {
        "C": "<uuid of C>"
     }
  },
  {
    "uuid": "<uuid of C>",
    "content": {...}
  },
]

Result:
B is resolved in content A, but C is not resolved in content B.