nextcloud / nextcloud/cookbook
Unicode fraction are not managed as ingredient's amount
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 641
- Forks
- 113
- Avg merge
- 21h 31m
- Merged PRs (30d)
- 26
Description
Hello,
The "bug" is rather simple to describe. I have no idea if it's simple to fix :)
This ingredient item show the warning sign, saying it cannot be parsed and understood
¼ cup fresh lime juice
If I change the unicode fraction to an ASCII one, it's ok:
1/4 cup fresh lime juice
Would it be possible to handle unicode fraction ?
Thanks
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
The issue names no file or test. Start by locating the ingredient-amount parsing entry point and reproduce the difference between ¼ cup fresh lime juice and 1/4 cup fresh lime juice. Done means the Unicode fraction is accepted as an ingredient amount without the warning sign, with a regression test covering the example.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100