-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Translation in the activity stream for shares which expired automatically #38631
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
Conversation
…red automatically
|
I'm not sure if this is right. Technically, the agent is like a virtual user that performs the action on behalf of another user. Having a "share_expire_author" doesn't fit here. What if there are more actions triggered during the share expiration? They could have the "share_expire_author" for a delete file action, which seems weird. Also note that whoever is listening for the delete file event won't likely take into account a "share_expire_author" agent, or won't receive any special treatment. I'd prefer to reuse the "automation_author" in this case and try to figure out if the share has expired in a different way. A "cli_author" seems to generic for this case, but we could use a different author. |
What do you think of expanding the event parameters here by core/lib/private/Share20/Manager.php Line 1110 in 4d11dd4
This way we could use this information in the activity app and add it as param. The author could be |
|
That's fine |
Co-authored-by: Jan Ackermann <[email protected]>
|
@jvillafanez I implemented it the way you suggested. Some changes are required in the activity app for this, see owncloud/activity#944. We basically now use the automation author and the |
|
Kudos, SonarCloud Quality Gate passed! |
Description
Add a proper translation in the activity stream for shares which expired automatically. Previous to this, the expiry was authored by a user, which is technically not true.
Related Issue
Screenshots (if appropriate):
Types of changes
Checklist: