Uploaded image for project: 'Magnolia REST Framework'
  1. Magnolia REST Framework
  2. MGNLREST-190

Reference resolvers should work more than 1 level deep

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2.1.4
    • Component/s: None
    • Labels:
      None
    • Release notes required:
      Yes
    • Epic Link:
    • Sprint:
      SPA Editor 9, SPA Editor 10
    • Story Points:
      8

      Description

      User Story:

      As a developer I can configure a Delivery endpoint to provide more then one level of reference resolving so that clients of the endpoint can get all of the information they require in one request.

      Notes:

      Currently the reference resolver can only resolve one level deep which is useful but often does not meet a clients of the endpoints requirements.

      For the SPA Editor epic, this is important if a page references a content item which then references an asset. A common case.

      For example to get the full information for a tour (from the travel demo) I need

      • the information of the tour node.
      • the information of the tourTypes.
      • the asset referenced  by the tourTypes (to get its icon.)

       

        Checklists

        Acceptance criteria

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                jsimak Jaroslav Simak
                Reporter:
                czimmermann Christopher Zimmermann
                Votes:
                6 Vote for this issue
                Watchers:
                12 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:
                  Date of First Response:

                    Checklists

                    DoD

                      Time Tracking

                      Estimated:
                      Original Estimate - Not Specified
                      Not Specified
                      Remaining:
                      Remaining Estimate - 0d
                      0d
                      Logged:
                      Time Spent - 6h 38m
                      6h 38m