Sabin Panta

What about sharing spaces? @saw-jan

@saw-jan should this `acceptance/features/apiReshare/resharing.feature` file be refactored?

I think anyone working in this issue, it would be easier to work as folderwise.

@rhafer @2403905

At the moment, multiple unmount request gives `400 status code`.

imo should be 404 as the shared resource gets deleted in those scenarios.

The bad request can only be the case if the value of `resource-id` doesn't match the format or is empty. https://github.com/owncloud/ocis/blob/590a40d979c73d73f4cb72314135b6445480c6c2/tests/acceptance/features/apiSharingNg/enableDisableShareSync.feature#L302 Here we enable sync where there is no resource...

On the master , there is no need to send the item name in body However, on stable 5, such should be done. ``` { "name": "test.txt", "remoteItem": { "id":...

For ~~declining~~ disabling sync an upcoming share ``` curl -X DELETE 'https://host.docker.internal:9200/graph/v1beta1/drives/{drive-id}/items/{item-id}' -u username:password ``` This will change @client.synchronize property of the item to false (disable sync) which refer to...

For ~~accepting pending share~~ enabling share sync ``` curl -X POST 'https://host.docker.internal:9200/graph/v1beta1/drives/{share-Space-Id}/root/children' -d '{ "remoteItem": { "id":"'remote-item-id" } }' ``` ~~This request returns drive item . `remote-item-id` and `permission-id` can...