nextcloud / nextcloud/cookbook
Build all cookbook tables from scratch
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 641
- Forks
- 113
- Avg merge
- 21h 31m
- Merged PRs (30d)
- 26
Description
After the change in PR #297 the database might get into a stale state. Thus, it might be favorable to have a GUI based way to drop all entries and rebuild the whole index from scratch. This breaks down to the following steps:
- Removal via API of all recipes (of a single user or all depending on folder structure)
- Readding of all related recipes
The update process might take quite some time. To avoid issues as described in #218 it would be favorable to use multiple AJAX requests to parse a small number of files (10 or so) per API request.
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 reviewing PR #297 and issue #218, then trace the recipe removal and re-adding APIs and the GUI update flow. Done means the GUI can rebuild all or selected recipe indexes in small AJAX batches without leaving the database stale.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, database, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100