You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Libre Graph specs reads on /drives/{id}/items/{id} (GET), a narrowly-scoped PATCH (only @UI.Hidden), DELETE (share-jail unmount only), and GET /content (#38, merged). Several MS Graph write endpoints are missing or incomplete. Consumers fall back to WebDAV for write ops and pay an extra Graph round-trip per path segment to resolve the resulting driveItem (concrete example: opencloud-eu/n8n-nodes-opencloud#11).
already broad enough (line 1280 describes recycle-bin behavior; example at line 1298 uses a share-jail-shaped id and could be supplemented with a normal example)
POST /copy: MS Graph returns 202 Accepted + monitor URL (no body); a synchronous variant for fast copies (body containing the destination driveItem) would let clients skip the monitor.
PATCH /items/{item-id}: name and parentReference combinable in one request; response is the updated driveItem. Cross-storage moves are inherently non-instant and should be rejected with a structured error, matching today's WebDAV 502.
Libre Graph specs reads on
/drives/{id}/items/{id}(GET), a narrowly-scopedPATCH(only@UI.Hidden),DELETE(share-jail unmount only), andGET /content(#38, merged). Several MS Graph write endpoints are missing or incomplete. Consumers fall back to WebDAV for write ops and pay an extra Graph round-trip per path segment to resolve the resultingdriveItem(concrete example: opencloud-eu/n8n-nodes-opencloud#11).Endpoints needed for MS Graph parity:
POST /items/{item-id}/children(non-root)PUT /items/{item-id}/contentPOST /items/{item-id}/copyPATCH /items/{item-id}(rename / move)nameandparentReferencebeyond@UI.HiddenDELETE /items/{item-id}(normal drive items)GET /items/{item-id}/children(non-root)GetDriveItemChildren)Notes on individual endpoints:
PUT /content: returns the uploadeddriveItem(201 + driveItem), so clients can drop the post-upload resolve walk. feat: Add @microsoft.graph.downloadUrl annotation and /content endpoi… #38 covered the download direction.POST /copy: MS Graph returns202 Accepted+ monitor URL (no body); a synchronous variant for fast copies (body containing the destinationdriveItem) would let clients skip the monitor.PATCH /items/{item-id}:nameandparentReferencecombinable in one request; response is the updateddriveItem. Cross-storage moves are inherently non-instant and should be rejected with a structured error, matching today's WebDAV 502.Related (in flight):