See resource owner in share panel

[PVince81]

• Story: https://github.com/owncloud/enterprise/issues/3773

• show resource owner for direct share: Added collaborator entries for owner and resharer #2915

• show resource owner for share inherited from parent resource (with "via"): Also show owner and resharer for indirect shares #2918

  • REQUIRES: Read and cache share information from local and parent folders #2894
  • "via" icon must use "redo" "exit_to_app" icon

• REQUIRES: additional info field also for owner and resharer: Return additional info for owner and recipient in share response core#36823

• reuse branch "share-indirect-info" for some attempts at buildling the UI. We could reuse this and populate with real data.

[PVince81]

Direct share

Reshare

Logged in as Dave.
Received a reshare from Bob where the resource owner is Alice.

Indirect share through parent

Same as the "Reshare" scenario but showing indirect owner when inside a subdirectory.

Note: "via" icon will be changed to use the "redo" icon (forward arrow)

@pmaier1

[pmaier1]

Very cool 👌 the "via" part in the third screenshot feels still a bit strange to me but maybe this is because of the strange folder name :)

[PVince81]

yes, this is just a rough mock up to illustrate the idea.

we'll need to ellipsize the name

[PVince81]

@pmaier1 the proposed design above cannot work as there are scenarios where multiple resharers exist for the same resource:

1. "alice" share "test" with user "bob"
2. "alice" shares "test" with user "charlie"
3. "bob" shares "test" with user "dave"
4. "charlie" shares "test" with group "dave-group" (where dave is member).
5. log in as "dave" and query the incoming shares for "test"

=> The API will deliver two incoming share entries:

• shared with dave by bob (user share)
• shared with dave by charlie (group share)

Our solution for this is to display owner and all reshares as separate collaborator entries:

• Alice - Owner
• Bob - Resharer
• Charlie - Resharer

We need to keep in mind that the main use case is to find out who has access to the resource, so it's important to list all those people individually.