You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This feature will provide a more personalized and efficient experience for our users by taking their specific preferences and constraints into account during recipe calculation.
Implementation Details
For this feature I propose calculating the recipes and plans in Python as opposed to Go because of Python's superior data processing and storage libraries. I have contacted our TA to confirm that this is allowed and will update this issue regarding his response. Here are some features I plan to start working on.
Scraping. First I will need to scrape and store many recipes and information on them such as: cuisine type, cost, time to prepare, etc.
Storage. Then this data must be stored in either some sort of file (csv) or database for quick and easily access in Python. I am leaning towards using a csv.
Calculation. This will be where we take into account all user preferences to calculate their weekly plan. For now I will use preliminary preferences such as cuisine type and time to prepare and we can add more as we go.
I plan to start working on the data collection and provide an example user in our database so the frontend team can prepare a graphical display of the results.
Description
This feature will provide a more personalized and efficient experience for our users by taking their specific preferences and constraints into account during recipe calculation.
Implementation Details
For this feature I propose calculating the recipes and plans in Python as opposed to Go because of Python's superior data processing and storage libraries. I have contacted our TA to confirm that this is allowed and will update this issue regarding his response. Here are some features I plan to start working on.
I plan to start working on the data collection and provide an example user in our database so the frontend team can prepare a graphical display of the results.
Related to user stories in #2
The text was updated successfully, but these errors were encountered: