Replace JSConfigHelper with Capabilities
Open
Nobody has claimed this yet.
♻️ refactor
1. to develop
feature: files
technical debt
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
Currently JSConfigHelper contains settings that should be handled by Capabilities instead.
This would also allow other clients to access the values if necessary and turns it into a proper stable API which is currently not the case with the JS script being generated on-the-fly.
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 JSConfigHelper and Capabilities in the Nextcloud server code, then identify which settings currently live in the helper. Trace how those values are exposed to clients and determine the access path needed for a stable API. Done means the settings are handled by Capabilities and remain available to clients without generating the current JS configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100