mirror/opencloud
1
0
Fork 0
mirror of https://github.com/opencloud-eu/opencloud.git synced 2026-01-07 04:40:05 -06:00
Code Issues Packages Projects Releases Wiki Activity

Fix typos

Browse Source 
(cherry picked from commit 10babaf4c527d91825f70cea68065f44dc01b8da)
This commit is contained in:
Ralf Haferkamp
2024-02-28 16:14:10 +01:00
parent eb9af537b3
commit 693bc7b38f
3 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
changelog/unreleased/sharing-ng-mount.md
View File

@@ -1,6 +1,6 @@
Enhancement: graphs endpoint for mounting and unmounting shares
Functionality for mounting (accepting) and unmounting (rejecting) received
has been added to the graph API
shares has been added to the graph API.
https://github.com/owncloud/ocis/pull/7885

2
services/graph/pkg/service/v0/api_drives_drive_item.go
View File

@@ -57,7 +57,7 @@ func (s DrivesDriveItemService) UnmountShare(ctx context.Context, resourceID sto
}
// This is a a bit of a hack. We should not rely on a specific format of the item id.
// (But currently the ShareID is
// But currently there is no other way to get the ShareID.
shareId := resourceID.GetOpaqueId()
// Now, find out the resourceID of the shared resource

6
services/graph/pkg/service/v0/utils.go
View File

@@ -228,7 +228,7 @@ func cs3ReceivedSharesToDriveItems(ctx context.Context,
// the oldest share for the resource:
// '<sharestorageid>$<sharespaceid>!<share-opaque-id>
// Note: This means that the driveitem ID will change when the oldest
// shared is removed. It would be good to have are more stable ID here (e.g.
// share is removed. It would be good to have are more stable ID here (e.g.
// derived from the shared resource's ID. But as we need to use the same
// ID across all services this means we needed to make similar adjustments
// to the sharejail (usershareprovider, webdav). Which we can't currently do
@@ -320,8 +320,8 @@ func cs3ReceivedSharesToDriveItems(ctx context.Context,
if err != nil {
// TODO: define a proper error behavior here. We don't
// want the whole request to fail just because a single
// resource owner couldn't be resolved. But, should be
// really return the affect share in the response?
// resource owner couldn't be resolved. But, should we
// really return the affected share in the response?
// For now we just log a warning. The returned
// identitySet will just contain the userid.
logger.Warn().Err(err).Str("userid", userID.String()).Msg("could not get owner of shared resource")