Arnaud
b0849c3989
Six M-sized items from HANDOFF.md's new-features backlog: - Profile tabs: cooking-history stats (total cooked, last-cooked, streak) and a "cooked it" photo gallery, both owner-only - Display-time unit conversion (metric<->imperial) for recipe ingredients, respecting each user's unitPref; original value always shown alongside the conversion - Nutrition daily diary: per-day macro totals computed from cooking history x recipe nutritionData, compared against user goals - Pantry scan: real barcode lookup (zxing + Open Food Facts, no API key) with an AI-vision fallback for unbarcoded items, always confirm-before- insert, both paths tier/rate-limited like other AI features - Weekly digest email: new followers/comments/ratings + trending recipes, sent via a new `cron` Docker stage (alpine+crond+curl) and `digest-cron` compose service hitting a bearer-token-protected internal route - Meal-plan generation can now target a user's nutrition goals as a prompt-level nudge (recipes are AI-invented, not DB-sourced, so this can't be a hard macro constraint) Caught a real deploy-breaking issue while adding the cron stage: appending it after `runner` silently changed the Dockerfile's default build target, and `web`'s compose config didn't pin one — fixed by pinning `target: runner` explicitly. Verified with typecheck, lint, and three separate `docker build --target` runs (runner/cron/migrator) plus `docker compose config` validation. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
58 lines
2.0 KiB
TypeScript
58 lines
2.0 KiB
TypeScript
import type { Metadata } from "next";
|
|
import { headers } from "next/headers";
|
|
import { auth } from "@/lib/auth/server";
|
|
import { db, pantryItems, recipes, eq, or, inArray } from "@epicure/db";
|
|
import { asc } from "@epicure/db";
|
|
import { PantryManager } from "@/components/meal-plan/pantry-manager";
|
|
import { PantryPageHeader } from "@/components/pantry/pantry-page-header";
|
|
import { ExpiringSoonSuggestions } from "@/components/pantry/expiring-soon-suggestions";
|
|
import { scoreRecipesAgainstPantry } from "@/lib/pantry-match";
|
|
import { getPublicUrl } from "@/lib/storage";
|
|
|
|
export const metadata: Metadata = {};
|
|
|
|
export default async function PantryPage() {
|
|
const session = await auth.api.getSession({ headers: await headers() });
|
|
if (!session) return null;
|
|
|
|
const [items, candidateRecipes] = await Promise.all([
|
|
db.query.pantryItems.findMany({
|
|
where: eq(pantryItems.userId, session.user.id),
|
|
orderBy: asc(pantryItems.rawName),
|
|
}),
|
|
db.query.recipes.findMany({
|
|
where: or(eq(recipes.authorId, session.user.id), inArray(recipes.visibility, ["public", "unlisted"])),
|
|
with: { ingredients: true, photos: true },
|
|
}),
|
|
]);
|
|
|
|
const mappedItems = items.map((i) => ({
|
|
id: i.id,
|
|
rawName: i.rawName,
|
|
quantity: i.quantity,
|
|
unit: i.unit,
|
|
expiresAt: i.expiresAt?.toISOString() ?? null,
|
|
}));
|
|
|
|
const suggestions = scoreRecipesAgainstPantry(candidateRecipes, items)
|
|
.filter((s) => s.usesExpiring.length > 0)
|
|
.slice(0, 3)
|
|
.map((s) => {
|
|
const cover = s.recipe.photos?.find((p) => p.isCover) ?? s.recipe.photos?.[0];
|
|
return {
|
|
id: s.recipe.id,
|
|
title: s.recipe.title,
|
|
photoUrl: cover ? getPublicUrl(cover.storageKey) : null,
|
|
usesExpiring: s.usesExpiring,
|
|
};
|
|
});
|
|
|
|
return (
|
|
<div className="space-y-6">
|
|
<PantryPageHeader items={mappedItems} />
|
|
<ExpiringSoonSuggestions suggestions={suggestions} />
|
|
<PantryManager key={mappedItems.map((i) => i.id).join(",")} initialItems={mappedItems} />
|
|
</div>
|
|
);
|
|
}
|