Move RoomShareProvider registration to talk code
Open
Nobody has claimed this yet.
feature: api 🛠️
technical debt
- Dominant language
- PHP
- Stars
- 2.2k
- Forks
- 587
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
Since https://github.com/nextcloud/server/pull/24605 it is possible for apps to register a share provider.
Not sure how feasible it is, but if possible we should therefore move the Talk share provider registration to our code instead of having it hard coded in server.
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 reading Nextcloud server pull request 24605 and locating the current hard-coded RoomShareProvider registration in the server. Determine whether Talk can register the provider itself; done when the registration is in Talk code and no longer hard-coded in the server.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100