-
Notifications
You must be signed in to change notification settings - Fork 187
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
Activities. Renaming file with file-id gives move activity instead of rename #9744
Comments
And what are the definitions/requirements for the words "move" and "rename"? "MOVE" (an HTTP method) and "mv" (a Linux command line command) are things that "move" where a file is in the file-system hierarchy. Sometimes the file stays in the same folder, but its name is different. In that case, end-users tend to say that the file has been "renamed". Sometimes the file goes to another folder, and its name remains the same. I suppose that is "move". Sometimes the file goes to another folder, and with a different name - that is a "move and rename"? |
For the ocis server there is no difference between For user facing notifications (activities/notifications/...) we change the naming so the user isn't confused. We use a simple logic everywhere. If the parent folder stays the same, this is a rename. Everything else is considered a move. So:
The server would consider this a move, not a rename. This is also the reason for this bug. Since we address the items by itemID, the path of these items will be empty, hence the server will consider this a rename. The fix is probably somehow related to #9712. Our events do not contain enough data to reliably reconstruct information from them. |
Describe the bug
lorem.txt
WIth file path:
The text was updated successfully, but these errors were encountered: