Parse recipes upon outputting instead of parsing
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
Start by mapping the recipe import and saving flow, then inspect how the API endpoints currently parse and format recipes. Define the minimal information-preserving import model and a separate output structure; done means existing recipe information survives import and the API can support additional formats.
Written by the indexing model from the issue text.
Description
Currently, we are parsing the recipe in a strict manner and trying to format it according to our needs. This might throw away information that is lost after the initial import and cannot be restored.
We should only do minimal parsing during the import and saving of recipes. Instead, we should have a clear structure on how to generate a well-suited output of the API endpoints. That will allow us to support other formats as well (see e.g. #138 #831 etc).
I am aware that this is a big undertaking but this might help to build a better understanding in the long term.
I assume it would be a good approach to generate an internal data structure that is simpler to use and parse than plain arrays in PHP. It might be favorable to implement a Visitor pattern on an abstract syntax tree to generate the solution.
- Dominant language
- HTML
- Stars
- 642
- Forks
- 113
- Avg merge
- 21h 31m
- Merged PRs (30d)
- 26
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.
More from nextcloud/cookbook
-
bug Frontend
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Frontend
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
github_actions maintenance
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
All issues in nextcloud/cookbook
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getgrav/grav-plugin-api#45 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·