nextcloud / nextcloud/cookbook
Update nutrition information with recalculated serving number
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 641
- Forks
- 113
- Avg merge
- 21h 31m
- Merged PRs (30d)
- 26
Description
Describe the solution you'd like
Currently, the nutrition number is not updated when the servings are updated. As a result, The nutrition is always based on the "stored" serving number. It should be updated in the Frontend in real-time once the servings are changed (similarly to the ingredients).
This was extracted from #1665.
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 tracing the frontend serving-count update flow and compare it with the existing real-time ingredient updates described in this issue and extracted from #1665. Done means nutrition information recalculates immediately when servings change, rather than remaining based on the stored serving number.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100