nextcloud / nextcloud/cookbook
Import recipes with a dedicated JSON graph
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 641
- Forks
- 113
- Avg merge
- 21h 31m
- Merged PRs (30d)
- 26
Description
In general, it is possible to use a @graph entry to define a JSON Schema object with references and more complex structures.
Our current importer is not able to cope with this situation. There is simply speaking no recipe found. This should be solved by creating a more stable and more robust import parser.
There are a few issues on the tracker that all boil down to this root cause. This one should be considered the central issue to tackle all these pages.
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 locating the current recipe importer and parser, then reproduce an import from a page whose structured data uses a @graph entry with JSON Schema references. The issue names no files or tests, so first map the existing importer flow and related tracker issues. Done means recipes are found and imported reliably from these more complex JSON structures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100