-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Provide avatar URL on share information #11406
Comments
GitMate.io thinks possibly related issues are #9182 (Just a question // Feature request // Pretty Share URL), #4334 (Improve sharing email information), #6881 ([Suggestion] Nice urls: make share links becoming nice), #2658 (Sharing and permissions), and #1575 ([Feature Request] Add configuration for "Sharing URL"). |
cc @rullzer maybe also something for you if you have some time. It is probably not that hard, someone "just" need to find the time to do it 😉 |
Adding the URL there should not be that hard. But adding the etag is a bit hard and a bit weird. It requires a lot of additonal logic with no real point imo. I'd vote to just add the link to the avatar. |
The idea with eTag was that clients then do not have to query the avatar url as they directly know if an avatar is out of date. |
Can we have this for NC17? Please :-) |
Is this still needed? |
True, this is already done via nc:sharees. |
Currently we "only" get infos on user who shared with "me" separate, via
http://localhost/nc/ocs/v2.php/apps/files_sharing/api/v1/shares?path=/123&reshares=true&subfiles=true&shared_with_me=true
Every client now has to build the avatar url by its own.
As discussed with @schiessle, this should be simplified, so that the avatar url is generated on server side and clients can directly retrieve them.
Please with eTags 👍And, if possible, for all users listed in the response (sharee and share owner)
(planned for NC15)
The text was updated successfully, but these errors were encountered: