fix: use own workspace endpoint instead of PROPFIND properties #2677
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
7cf78b0 to
3a7b86a
Compare
|
/compile |
|
/backport to stable24 |
juliusknorr
approved these changes
Jul 6, 2022
a898f71 to
ccb3c09
Compare
|
/compile amend / |
With a lot of subdirectories the depth=1 PROPFIND will take quite a long time. It has to look for workspace files in all the subdirectories. Stop overloading the PROPFIND and rely on our own workspace endpoint for that particular directory instead. Signed-off-by: Max <max@nextcloud.com> Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
ccb3c09 to
ecb59d2
Compare
8 tasks
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.
With a lot of subdirectories the depth=1 PROPFIND will take quite a long time.
It has to look for workspace files in all the subdirectories.
Stop overloading the PROPFIND and rely on our own workspace endpoint
for that particular directory instead.