Generic extension point for creating team resources
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 177
- Forks
- 68
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 60
Description
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Feature request
**Which Nextcloud Version are you currently using: 34 / 35 ** (see administration page)
Is your feature request related to a problem? Please describe.
Cannot add a create button for a custom team resource in Team Details view.
Describe the solution you'd like
It would be nice to add a way to register a resource creation mechanism for custom resources.
Describe alternatives you've considered
I checked the code of version 34 / 35 / 36 and found no solution as create buttons list is hardcoded.
Additional context
I am working on the Olvid application for Nextcloud, which allows creating an Olvid discussion associated with a Nextcloud group/team.
I am able to list Olvid discussions associated with a team, but I cannot create a new discussion from the circle management view.
It might also be nice to add a way to edit circle resources, but for now I can work around that by setting a link to my app on the resource.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the hardcoded create-button list used by the Team Details or circle management view, comparing the code in versions 34, 35, and 36. Define an extension point that lets custom resources register creation mechanisms, then verify that an Olvid discussion can be created from the team view without breaking existing resource actions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100