The previously created /image POST endpoint is extended to receive arbitrary image name, upload that to AWS S3 bucket, then create a database instance with that particular image, or update it if there had already been an instance for that user for that day
Spoonacular API is introduced which provides us nutritional data and recipe names about the ingredients we send as a query string. getRecipe and getNutrition functions are defined and are responsible for making the API calls
A POST endpoint /ingredients is created where a list of ingredients is received from the frontend which are forwarded to the Spoonacular API
After receiving data from the API the endpoint performs some data manipulation, and both sends the nutrition, ingredient and recipe data to the frontend as well as updates the corresponding database instance created at the /image POST endpoint with the corresponding ingredients, and the total nutritional data for that day.
What this pull request does: