fix: Remove duplicate propfind call #50109
Merged
+40
−35
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
artonge
added
3. to review
nfebe
approved these changes
Jan 9, 2025
artonge
force-pushed
the
artonge/fix/remove_duplicate_propfind_call
branch
2 times, most recently
from
0074957 to
bff81de
Compare
|
/compile / |
artonge
force-pushed
the
artonge/fix/remove_duplicate_propfind_call
branch
from
ffb296a to
45ec577
Compare
Merged
artonge
force-pushed
the
artonge/fix/remove_duplicate_propfind_call
branch
3 times, most recently
from
309d918 to
e20282b
Compare
This also was an XHR call which is not going through the end to end encryption proxy Signed-off-by: Louis Chemineau <[email protected]>
Signed-off-by: Louis Chemineau <[email protected]>
artonge
force-pushed
the
artonge/fix/remove_duplicate_propfind_call
branch
from
e20282b to
5faaeca
Compare
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.
This also was an XHR call which is not going through the end-to-end encryption proxy