Open Zhilin-Huang opened 4 years ago
The idea of creating a recipe is to use the existing food stored in the food list to plan out a estimated food plan for the user. It uses common foods eaten by the user and stored to generate a food plan based on user's eating habits. Without any food being stored, it is understood that no recipe or foodplan can be generated for the user.
However, this issue is acknowledged but should not affect user experience or functionality of the application.
Team chose [response.NotInScope
]
Reason for disagreement: While it is true that 'without any food being stored, no recipe or foodplan can be generated for the user', shouldn't the user at least get a warning/hint for this? When I tried generating a recipe and saw an empty result, I had to figure out by myself what has caused this problem and it took quite some time. So instead of making the user wonder what is happening and what is the problem when they get an empty recipe, doesn't it make more sense to just let the users know that a recipe cannot be generated with an empty food list?
Also, it seems useless to display an empty recipe as it does not really mean anything and could be confusing for the users.
Recipe recommendation does not report error and only gives empty recipe when food list is empty. The application shall let the users know recipe cannot be generated instead of giving empty recipe which confuses the users.
Appears only in situations where the food list is empty and causes a minor inconvenience.