nextcloud / nextcloud/richdocuments
Ensure empty templates are updated if changed from previous versions
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 453
- Forks
- 147
- Avg merge
- 14h 54m
- Merged PRs (30d)
- 83
Description
Currently it is required to manually run occ richdocuments:update-empty-templates but we should instead just have a migration step. However this needs to be handled with some care as there is an undocumented way that people can replace empty template files with their own in appdata.
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 with the existing occ richdocuments:update-empty-templates command and trace how empty template files are identified and updated. Define the migration behavior so changed templates are applied while preserving user-replaced files in appdata; done means manual command execution is no longer required without overwriting those custom files.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100