Use provisioning api for config changes
Open
Nobody has claimed this yet.
feature: api 🛠️
medium
technical debt
- Dominant language
- PHP
- Stars
- 2.2k
- Forks
- 587
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
Newly added /api/v1/config/users with https://github.com/nextcloud/server/pull/32560 should allow us to get rid of our own settings controller
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 existing settings controller and its config-change entry points, then inspect the newly added /api/v1/config/users endpoint and nextcloud/server#32560. Done means config changes use the provisioning API and the spreed-specific settings controller can be removed without changing the intended behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100