-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rewire dav files endpoint to home (better approach) #1125
Rewire dav files endpoint to home (better approach) #1125
Conversation
hmmm, so did my PR magically fix many issues ? @phil-davis |
I've pushed a fix for the OPTIONS request, that should at least fix the Litmus tests |
there was a bug to the fallback, fixed now expecting more tests to pass now |
If the user specified in the dav files URL matches the current one, rewire it to use the webDavHandler which is wired to the home storage. This fixes path mapping issues.
Rebased onto master which has #1124 merged now. I've also adjusted the expected failures. It is possible that the rewiring has fixed some issues very indirectly. |
Cool! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All the trashbin scenarios that have started passing are for the "new" dav-path. So this PR definitely does fix stuff.
apiTrashbin/trashbinFilesFolders.feature:273 | ||
apiTrashbin/trashbinFilesFolders.feature:274 | ||
apiTrashbin/trashbinFilesFolders.feature:275 | ||
apiTrashbin/trashbinFilesFolders.feature:276 | ||
apiTrashbin/trashbinFilesFolders.feature:277 | ||
apiTrashbin/trashbinFilesFolders.feature:278 | ||
apiTrashbin/trashbinFilesFolders.feature:289 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are Scenario Outline Examples for the "new" dav-path. The Examples for the "old" dav-path were already passing. So the "rewiring" in this PR has fixed some issue with the "new" dav-path. That is "a good thing" (tm)
apiTrashbin/trashbinRestore.feature:295 | ||
apiTrashbin/trashbinRestore.feature:310 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are both Examples for "new" dav-path. The example for "old" dav-path at 294 and 309 were already passing.
If the user specified in the dav files URL matches the current one,
rewire it to use the webDavHandler which is wired to the home storage.
This fixes path mapping issues.
Obsoletes #1120