feat: add @libre.graph.lock facet to driveItem - #59
Open
dschmidt wants to merge 1 commit into
Open
Conversation
dschmidt
marked this pull request as ready for review
August 9, 2026 13:26
dschmidt
requested review from
butonic,
dragotin,
fschade,
kulmann,
micbar and
rhafer
as code owners
August 9, 2026 13:26
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a read-only
@libre.graph.lockfacet to driveItem, present while the item is locked for writing. CarriesappName,ownerName,lockedDateTimeandexpirationDateTime, matching what the WebDAVlockdiscoveryresponse exposes today viad:activelockplus theoc:ownernameandoc:locktimeextensions.MS Graph has no lock facet on driveItem, the closest concept (
publicationcheckout) is a different mechanism, hence the@libre.graphnamespace.