nextcloud / nextcloud/richdocuments
Drop user template directory
Open
Nobody has claimed this yet.
1. to develop
feature: templates
good first issue
technical debt
- Dominant language
- JavaScript
- Stars
- 453
- Forks
- 147
- Avg merge
- 14h 54m
- Merged PRs (30d)
- 83
Description
Since there is a user wide templates folder in Nextcloud now we should drop the user option to set a template and only make use of the core one.
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 user option for selecting a template and the code that handles the core template. Trace where the option is exposed and consumed, then verify that template handling uses only the core template and that the user option is no longer available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100