Details

      Description

      As a developer using the REST API I want to list children by specifying a relative path to the folder (that is relative to a specified parent id, including well-known aliases).

      For example, allow the following:

      /nodes/{parentId}/children?relativePath=/Sites/mysite/documentLibrary

      Acceptance Criteria

      • Does the /nodes/parentId/children URL accept a GET request with optional "relativePath" query param and return a 200 status code if successful?
      • Can the "relativePath" query param optionally start with a "/" character ?
      • Can the "relativePath" query param resolve to a folder (since children will be listed) ?
      • Does the /nodes/parentId/children URL return a 400 response if the resolved node is not a folder?
      • Does the /nodes/parentId/children URL return a 404 response if the resolved node (based on relativePath) does not exist?
      • Does the /nodes/parentId/children URL return a 404 response if the parentId in the path param does not exist?
      • Does the /nodes/parentId/children URL return a 400 response if the parentId in the path param does does not represent a folder?
      • Does the /nodes/parentId/children URL return a 403 response if the current user does not have permission to return resolved node ?
      • See also RA-639 for more A/C

        Attachments

          Issue Links

            Structure

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  gcornwell Gavin Cornwell [X] (Inactive)
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel