{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/e984555bc55d44f791a9a549db577d6a\" frameborder=\"0\" width=\"1726\" height=\"1294\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1294,"width":1726,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1294,"thumbnail_width":1726,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/e984555bc55d44f791a9a549db577d6a-3c5d46a2e0f2c641.gif","duration":1383.957,"title":"Build Recipe API App, Frontend and Backend","description":"This Loom walks through the Build Recipe API app, covering its front end, API endpoints, database design, and key implementation challenges. The front end lets users list recipes and add or delete recipes with fields for name, ingredients, instructions, selected chef, and recipe category (pescatarian, vegan, or vegetarian), plus manage chefs with name and email. The API supports fetching recipes by unique ID, creating recipes via POST, and deleting by unique ID, with documentation and screenshots included in a comprehensive GitHub README. The creator spends most time explaining table creation with users and categories referenced as foreign keys in the recipes table, and describes two front end and backend challenges, including a major React rendering bug caused by missing ID keys in returned user and category data."}