I'm currently needing fake data for recipe and ingredients, including separated lists for vegetables, fruits, nuts etc.
I'd imagine something like this:
enum Category {
Fruit,
Vegetable,
Nut,
// etc...
}
Ingredient(category: Option<Category>);
Ingredients(count: usize, category: Option<Category>);
Recipe();
Recipes(count: usize);As of now, I do not have recipe steps implemented but might add them later on. One thing that might actually be better would be moving the Ingredient call to a separate call like Fruit(), Vegetable(), Nut() and have Recipe re-use them. That way, they are not coupled to recipes and should make it clear that they can be used by their own.
If there is interest I can open a PR so you can merge my additions back into master.
I'm currently needing fake data for recipe and ingredients, including separated lists for vegetables, fruits, nuts etc.
I'd imagine something like this:
As of now, I do not have recipe steps implemented but might add them later on. One thing that might actually be better would be moving the
Ingredientcall to a separate call likeFruit(), Vegetable(), Nut()and haveRecipere-use them. That way, they are not coupled to recipes and should make it clear that they can be used by their own.If there is interest I can open a PR so you can merge my additions back into master.