From dff70e0be4f6eb849aa85935d58146ef468d9f2b Mon Sep 17 00:00:00 2001 From: "A.Unger" Date: Fri, 8 Oct 2021 14:07:58 +0200 Subject: [PATCH] add docs for editing a Space --- docs/extensions/storage/spaces.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/extensions/storage/spaces.md b/docs/extensions/storage/spaces.md index f3f811f7ca..7fe3fb7c2b 100644 --- a/docs/extensions/storage/spaces.md +++ b/docs/extensions/storage/spaces.md @@ -7,6 +7,8 @@ geekdocEditPath: edit/master/docs/extensions/storage geekdocFilePath: spaces.md --- +{{< toc >}} + ## Editing a Storage Space The OData specification allows for a mirage of ways of addressing an entity. We will support addressing a Drive entity by its unique identifier, which is the one the graph-api returns when listing spaces, and its format is: @@ -40,6 +42,8 @@ This is an extract of an element of the list spaces response. An entire object h } ``` +### Updating a space property + Having introduced the above, one can refer to a Drive with the following URL format: ```console @@ -55,7 +59,7 @@ curl -X PATCH 'https://localhost:9200/graph/v1.0/Drive("1284d238-aa92-42ce-bdc4- The previous URL resource path segment (`Drive(1284d238-aa92-42ce-bdc4-0b0000009157!07c26b3a-9944-4f2b-ab33-b0b326fc7570)`) is parsed and handed over to the storage registry in order to apply the patch changes in the body, in this case update the space name attribute to `42`. Since space names are not unique we only support addressing them by their unique identifiers, any other query would render too ambiguous and explode in complexity. -## Updating a space description +### Updating a space description Since every space is the root of a webdav directory, following some conventions we can make use of this to set a default storage description and image. In order to do so, every space is created with a hidden `.space` folder at its root, which can be used to store such data.