feat: add lockInfo to driveItem - #59
Conversation
|
The MS Graph Beta endpoint has We can use it as is AFAICT. The driveItem.lockInfo has It has no appName, bet we can add it as a @libre.graph.appName property on the lockInfo. Related: Remarks:
|
|
Tremendous find, that landed in the beta docs on 2026-06-30, a few weeks before this PR was drafted. Reworked to lockInfo as is plus The lock/releaseLock endpoints are left for their own PR, WebDAV LOCK stays the write path for now. |
7fa1057 to
8d41b1f
Compare
8d41b1f to
63b11ce
Compare
4b11d41 to
e2c925d
Compare
Adds lock metadata to driveItem as the top-level
lockInfoproperty, matching the MS Graph beta lockInfo resource (published 2026-06-30):lockType(none,exclusive,shared,unknownFutureValue),createdDateTime,expirationDateTimeandowners. One extension:@libre.graph.appNamecarries the application holding the lock (WOPI/app locks), which MS Graph does not model.Everything is read straight off the CS3 lock:
lockTypefromLock.Type,createdDateTimefrom thelocktimeopaque,expirationDateTimefromLock.Expiration,ownersfromLock.Userplus thelockownernameopaque,@libre.graph.appNamefromLock.AppName. WebDAV exposes the same state only in mangled form (app name folded into thed:ownerstring, expiration as a relatived:timeout).The beta
POST .../lockandreleaseLockendpoints are not part of this PR; WebDAVLOCK/UNLOCKstays the write path for now. They can follow as their own PR (including whether to relax the 30 minute cap via config).