nextcloud / nextcloud/cookbook
Add Ability to Have Range of Serving Sizes
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 642
- Forks
- 113
- Avg merge
- 21h 31m
- Merged PRs (30d)
- 26
Description
Is your feature request related to a problem? Please describe.
In my experience, the serving size field only accepts a single integer value. Many recipes have ranges of expected servings based on a variety of factors. When I try to put in a range (e.g. 12-18) the results defaults to "1".
Describe the solution you'd like
Allow the "serving size" field to accept a range of serving sizes. (Solution potentially in the form of changing to a text field?)
Describe alternatives you've considered
If I would like a range I currently just put this in the description as a note, but a more flexible serving size field would be more convenient.
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
No files or tests are identified in the issue. Start by tracing the serving size field and its current integer handling, then determine how a range should be represented and displayed. Done means values such as 12-18 are accepted without defaulting to 1 and remain usable wherever serving size is shown.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100