-
Notifications
You must be signed in to change notification settings - Fork 12
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
fix(dav): Fix DAV functions to make work with them easier #725
Conversation
82188a7
to
77a929e
Compare
Codecov Report
@@ Coverage Diff @@
## master #725 +/- ##
==========================================
- Coverage 78.20% 77.94% -0.26%
==========================================
Files 17 17
Lines 390 390
Branches 109 107 -2
==========================================
- Hits 305 304 -1
- Misses 72 73 +1
Partials 13 13
|
Hummmm, this is a breaking change though. |
@skjnldsv basically every beta version currently was breaking ;-) There are two breaking changes here:
|
yes and no. What is the migration path for this change? |
Not much needed, querying favorites should work as before as the root is injected. The client now is configured with the base url as in our documentation: https://docs.nextcloud.com/server/latest/developer_manual/client_apis/WebDAV/basic.html#webdav-basics |
* `davGetClient` should default to the DAV remote URL instead of including the users root (to allow SEARCH) * `getFavoriteNodes` should work with any path * Add missing documentation Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
77a929e
to
d33096d
Compare
davGetClient
should default to the DAV remote URL instead of including the users root (to allow SEARCH)getFavoriteNodes
should work with any pathBecause especially the
getFavoriteNodes
function was copied from the files app, but there is no reason why it should be restricted in this library to only support favorites on/
but not on other paths (also the documentation said it would do).