Sebastian Fey

> Are both really required? Could'nt we just use tags only? tl;dr; I'd say no. 😄 Reasons being - We would completely break the existing data and workflows of current...

> @seyfeb do you think it is a good idea to update the `master` changelog when new releases are created on _foreign_ branches? Since we have witnessed that it might...

> Another issue, that might come up in the future: If there are recipes that allow multiple parts (dough, topping, filling) each with a list of instructions and ingredients, then...

@teledyn The parsing of the websites contain the recipe information is done in the backend. I think the parsing logic should be located in `lib/Helper/HTMLParser/HttpJsonLdParser.php` which extends an abstract parser...

I have some questions: As @christianlupus mentioned a tree-like structure: Is the requirement to support a tree of versions, such that one can have multiple branches of recipes developing in...

> > > Should any saved change create a new version or only if I actively create a “tagged recipe”? > > > > > > Thats what I was...

Same issue here. After selecting an image to be uploaded an error is logged in Firefox: ``` Uncaught (in promise) TypeError: t.imageData is undefined ``` wger version 2.3.0a2

> @seyfeb does this collide with your work currently? Definitely, as I touched almost everything in the frontend. At least, in the `RecipeView` I moved things around a lot. However,...

This is fixed in https://github.com/nextcloud/cookbook/pull/2115

Thank you for your suggestion. We follow the https://schema.org/Recipe for structuring the information. The `NutritionInformation` object [does not contain](https://schema.org/NutritionInformation) dietary information but only the nutritional values. If I understand you...