Difference between "Servings" and "Yield"? #4856
-
|
What problem has the introduction of the "Yield" fields solved, what's the use case and why do both "Servings" and "Yield" exist at the same time now? When would I use one instead of the other or both? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
It's worth checking out the discussion on the PR: #4489
While I would guess most recipes use one or the other, there are several instances where you could use both. For example, if you have a meatball recipe, you may yield 12 meatballs, but that may only serve 4 people (i.e. 3 meatballs per person). To address your first question: having a structured servings field enables several enhancements in the future (e.g. show me recipes that serve > 10 people). This is already possible in the API (since the API can work with arbitrary fields) however my plan is to build it into the frontend in the near future. |
Beta Was this translation helpful? Give feedback.
-
|
That makes sense, thank you for the quick response! |
Beta Was this translation helpful? Give feedback.
It's worth checking out the discussion on the PR: #4489
While I would guess most recipes use one or the other, there are several instances where you could use both. For example, if you have a meatball recipe, you may yield 12 meatballs, but that may only serve 4 people (i.e. 3 meatballs per person).
To address your first question: having a structured servings field enables several enhancements in the future (e.g. show me recipes that serve > 10 people). This is already possible in the API (since the API can work with arbitrary fields) howev…