-
Notifications
You must be signed in to change notification settings - Fork 184
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
Add ParentId in OCS and webdav REPORT responses #4727
Comments
And another use case: after deleting the current folder the web ui navigates up to the parent folder. That led me to the thought: Would be really helpful if we'd have the parentId in all propfinds as well. Saves us from doing a propfind on the parent path just for navigating there... from what you showed me last week this should be easy to achieve, right? |
REPORT requests are still pending. |
All done so far. The search index stores the parentID from now on. Existing items from the index will not have a
|
recreating the index only works when a non memory registry is used. Otherwise Try setting @rhafer @micbar in effect using our default in memory registry makes it impossible to use cli commands if they need to look up services ... |
TODO QA team:
|
Web offers a navigation into parent folders in various pages / situations:
Shares
section in the right sidebar of a subfolder or file of a shared parent folderIn order to solve owncloud/web#6247 we need to be able to include the file id of the respective parent into the navigation.
As a result, the GA blocking requirement is: Web needs the parent id of files/folders listed in OCS share and webdav REPORT responses.
Edit: The property already exists in the OCS APi and is called
file_parent
, hence a fitting name for WebDAV would beoc:file-parent
.Solution
Webdav PROPFIND
Note: the space root has no parent
OCS
List outgoing shares
List incoming shares
Search REPORT
The text was updated successfully, but these errors were encountered: