[MGNLREST-96] CLONE - Implement basic "listing" endpoint Created: 31/Jul/17  Updated: 06/Nov/17  Resolved: 11/Sep/17

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

Type: Task Priority: Neutral
Reporter: Mikaël Geljić Assignee: Hieu Nguyen Duc
Resolution: Fixed Votes: 0
Labels: rest
Remaining Estimate: 0d
Time Spent: 3d 5.5h
Original Estimate: 5d

Issue Links:
Cloners
Relates
relates to MGNLREST-98 Wrap query results into a result object Closed
relation
is related to MGNLREST-99 Research possibility to move the Prov... Open
is related to MGNLREST-100 Research possibility to remove Provid... Closed
supersession
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: REST Headless bundle
Sprint: Saigon 107, Saigon 108, Saigon 109, Saigon 110, Saigon 111, Saigon 112, Saigon 113
Story Points: 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.



 Comments   
Comment by Hieu Nguyen Duc [ 08/Aug/17 ]

This branch is based on REST-93.
URI: https://goo.gl/bHmMQk

Comment by Dai Ha [ 12/Sep/17 ]

verified with magnolia-enterprise-pro-demo-bundle-5.6-20170911.202509-109-tomcat-bundle.

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