perf(Share20): Add interface to query all shares in a folder without filtering by user#52634
Merged
provokateurin merged 1 commit intomasterfrom May 8, 2025
Merged
Conversation
provokateurin
requested review from
sorbaugh and
yemkareems
and removed request for
a team
provokateurin
added
3. to review
Member
Author
|
/backport to stable31 |
come-nc
approved these changes
May 5, 2025
icewind1991
approved these changes
May 8, 2025
…filtering by user Signed-off-by: provokateurin <kate@provokateurin.de>
provokateurin
force-pushed
the
perf/share20/get-all-shares-in-folder
branch
from
1c180b5 to
ae16a28
Compare
provokateurin
removed
the
pending documentation
Merged
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
4 participants
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.
Summary
The providers didn't have an efficient way to query all shares in a folder without filtering by user and the current solution which was doing it for each node in the folder caused performance issues.
Checklist