feat: add pendingOperations facet to driveItem - #60
Draft
dschmidt wants to merge 1 commit into
Draft
Conversation
dschmidt
force-pushed
the
feat/driveitem-pending-operations
branch
from
August 9, 2026 16:09
9601ded to
f7095a6
Compare
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 the MS Graph
pendingOperationsfacet to driveItem with thependingContentUpdatemember, present while an update to the item's content has not completed, for example post-processing such as virus scanning after an upload. Semantics match MS Graph with one difference: while the facet is present, content requests fail with425 Too Early, they do not return stale data.queuedDateTimemay be absent.WebDAV PROPFIND exposes this state as a propstat with status
425 TOO EARLY, Graph listings use this facet instead.