feat: retrieve audio and location metadata #10125
Merged
Conversation
This file contains 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
|
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes. |
JammingBen
approved these changes
Dec 6, 2023
|
Kudos, SonarCloud Quality Gate passed!
|
delete-merged-branch
bot
deleted the
feature/audio-and-location-metadata
branch
ownclouders
pushed a commit
that referenced
this pull request
Dec 6, 2023
…tadata feat: retrieve audio and location metadata
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Load
audioandlocationmetadata in propfinds.Related Issue
Motivation and Context
I want to make metadata available to extensions, especially sidebar panels (c.f. #10111)
MS Graph API returns
audioandlocationfacets as soon as they are available for adriveItem- assuming oCIS wants to stay compatible with that and that we are going to switch to graph api at some point, I think we don't need to add complexity for loading these props only on demand.Screenshots (if appropriate):
Types of changes
Checklist: