-
Notifications
You must be signed in to change notification settings - Fork 141
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
Manage the Nextcloud trash #4432
Conversation
The path for files/directories inside the NextCloud trashbin are NOT their parent path + their name, but also contains a suffix. So, we need to add the path to the response to allow the clients to make operations on them.
"attributes": { | ||
"type": "directory", | ||
"name": "Old", | ||
"path": "/trash/Old.d93571568", |
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.
@cballevre be careful, the path for things inside the trash is a bit weird and cannot be computed with just the parent and the name, so it was added to the response
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.
Interesting clarification. I saw that you added the path
everywhere. In cozy-client, I add a second attribute named parentPath
. It corresponds to the folder path. This is to make it easier to replay requests with sift.js (commit with some explanation). Wouldn't it make sense to add it to the back as well, so we wouldn't have to calculate anything on the front?
No description provided.