Add related resources panel component

[Pytal]

Add new component for nextcloud/server#28320

Screenshot (Shared items tab in Talk)

@ArtificialOwl since this component will be used in other apps how do we fetch the related resources of a Talk conversation, Deck board, Calendar event, et cetera?

[ArtificialOwl]

@ArtificialOwl since this component will be used in other apps how do we fetch the related resources of a Talk conversation, Deck board, Calendar event, et cetera?

It should be working the same as for Files.
The url of the OCS endpoint is : /related/{providerId}/{itemId}

replace providerId by "talk" or "deck".
replace itemId by the string or int Id that identify the current browsed item (room for talk, board for deck)

[Pytal]

Keeping as draft for now

[PVince81]

how about renaming from "related resources list" to just "resources list" ? it's just a name change and it already makes it more generic. having a component that is able to list resources can be useful in its own way (even if they are not "related")

[Pytal]

how about renaming from "related resources list" to just "resources list" ? it's just a name change and it already makes it more generic. having a component that is able to list resources can be useful in its own way (even if they are not "related")

There's no "related resources list" string do you mean renaming the component to NcResourceList?

[PVince81]

how about renaming from "related resources list" to just "resources list" ? it's just a name change and it already makes it more generic. having a component that is able to list resources can be useful in its own way (even if they are not "related")

There's no "related resources list" string do you mean renaming the component to NcResourceList?

I meant that yes. But now going through the code I see that the logic is highly specific to that. I didn't think it would also contain the XHR requests for related resources and more logic. So the current code makes it very specific to related resources and is then reusable.

I still have mixed feelings for having this here, wondering if it shouldn't then be a different nextcloud repo and lib. On the other hand a specific lib for just 1-2 components feels like overkill. So perhaps we just move forward with this for now.

[PVince81]

👍

only one comment about accessible name
can also be resolved separately in case it becomes complicated

[Pytal]

I still have mixed feelings for having this here, wondering if it shouldn't then be a different nextcloud repo and lib. On the other hand a specific lib for just 1-2 components feels like overkill. So perhaps we just move forward with this for now.

Yeah this solution as well as the alternative would incur the benefits and drawbacks detailed in nextcloud-libraries/nextcloud-vue-dashboard#407

[juliushaertl]

Note we branched off a stable6 branch and master will be the next major only compatible with Nextcloud 25+, so if needed please backport this pr also to stable6.

[PVince81]

related resources is planned for NC 25 only, so probably no backport needed