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

CLONE - Implement basic "listing" endpoint

    XMLWordPrintable

Details

    • Task
    • Resolution: Fixed
    • Neutral
    • 2.0
    • None
    • None
    • Saigon 107, Saigon 108, Saigon 109, Saigon 110, Saigon 111, Saigon 112, Saigon 113
    • 8

    Description

      What does listing mean by default?

      • queries? or visiting?
        • list-views in content apps work with queries—via AbstractJcrContainer
        • assuming we get the primary node-type info from somewhere (e.g. CT definition)

      What does the user need

      • flat list, e.g. from upcoming events component
      • node tree?
        • JCR-specific endpoints only?
        • pass absolute path
        • depth query param—same as NodesEndpoint
      • Assuming we have a notion of one or more primary node-types
      • e.g. "fruit" is primary, folders are secondary

      Could be based on MGNLREST-93; should belong in the new delivery module.
      Outcome could be an array of "nodes/objects" (via simple format) +/- response metadata.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                hieu.nguyen Hieu Nguyen Duc
                mgeljic Mikaël Geljić
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Task DoR

                    Time Tracking

                      Estimated:
                      Original Estimate - 5d
                      5d
                      Remaining:
                      Remaining Estimate - 0d
                      0d
                      Logged:
                      Time Spent - 3d 5.5h Time Not Required
                      3d 5.5h