fix: Use relative paths to dav root #2417
Merged
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.
@susnux After #2392 and #2414 the filename attribute is still different from before. Before we used to have the relative path based on the user home or public share, how it actually includes the files/userId/ dav root.
My quick fix proposal would be to change the root that the dav client uses so the path it returns for filename is again relative to that root.
We could otherwise of course adjust apps that make use of that path, but I think the path relative to the root is more useful then the full dav path.
Before the refactor: /MyFolder/test.odt
After the refactor: /files/admin/MyFolder/test.odt
After this PR: /MyFolder/test.odt
Test CI runs for text, richdocuments: