josh/YesChef
1
0
Fork 0
Code Pull Requests Actions Packages Projects Releases Activity

Add structured quantities + units to shopping list items

Browse Source 
Mirrors the Phase 2 work on RecipeIngredient: ShoppingListItem grows
Quantity (decimal), UnitOfMeasureId / FamilyUnitOfMeasureId, IsApproximate,
and QuantityNote. The recipe-to-list copy now carries structured fields
verbatim instead of folding them into the free-form Name, and the
unit-in-use guard now also blocks deleting a family unit that's referenced
by a shopping list item.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Josh Rogers
2026-05-13 21:18:26 -05:00
parent c7f9c31952
commit fb1bc2b7e1
11 changed files with 1606 additions and 64 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/backend/YesChef.Api/Features/Units/UnitEndpoints.cs
+6 -4
View File
@@ -119,10 +119,12 @@ public static class UnitEndpoints
var unit = await db.FamilyUnitsOfMeasure.FirstOrDefaultAsync(u => u.Id == id && u.FamilyId == familyId);
if (unit is null) return Results.NotFound();
// Block deletion when any recipe ingredient still references the
// unit. (ShoppingListItem will gain the same check in Phase 3.)
var inUse = await db.RecipeIngredients.AnyAsync(i => i.FamilyUnitOfMeasureId == id);
if (inUse) return Results.Conflict(new { error = "Unit is in use by one or more recipes." });
// Block deletion when any recipe ingredient or shopping list item
// still references the unit.
var inUseByRecipe = await db.RecipeIngredients.AnyAsync(i => i.FamilyUnitOfMeasureId == id);
if (inUseByRecipe) return Results.Conflict(new { error = "Unit is in use by one or more recipes." });
var inUseByList = await db.ShoppingListItems.AnyAsync(i => i.FamilyUnitOfMeasureId == id);
if (inUseByList) return Results.Conflict(new { error = "Unit is in use by one or more shopping lists." });
db.FamilyUnitsOfMeasure.Remove(unit);
await db.SaveChangesAsync();