Schema changes (require a single migration to apply): - User gains disclaimerAcceptedAt — null until the user accepts the medical disclaimer, blocks /profile until set (PRD §14.3) - New WeightEntry (PRD §5.2) — weight/measurements/notes encrypted at rest, energy/sleep/hunger left in the clear so we can produce aggregate analytics - New FastEvent (PRD §5.3) — symptoms/notes encrypted, protocol/status/timer in the clear; indexed on (userId, startedAt) - New Ingredient / Recipe / RecipeIngredient (PRD §5.1) — italian keto recipe database with macros and exclusion groups, ready for the matchmaking algo - New MealPlan / MealSlot — generated weekly plan with selected recipe and alternatives per (day, meal) - New enums: FastStatus, MealCategory, Difficulty, MealPlanStatus Web — disclaimer flow: - /welcome page (server component, requires auth) lists the 4 PRD-mandated points and surfaces the 3 mandatory checkboxes; submit triggers a server action that stamps disclaimerAcceptedAt and redirects to /profile - /profile redirects to /welcome whenever disclaimerAcceptedAt is null, so the disclaimer becomes a hard prerequisite for any sensitive page - New Italian copy under Welcome.* in messages/it.json - @ketopath/db added to apps/web dependencies (was indirect via @ketopath/auth) @ketopath/db re-exports the new models and enums. Run the migration before testing: `pnpm db:migrate --name onboarding_v1_recipes`. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
30 lines
429 B
TypeScript
30 lines
429 B
TypeScript
export { prisma } from './client.js';
|
|
export {
|
|
ActivityLevel,
|
|
CookingTime,
|
|
Difficulty,
|
|
FastStatus,
|
|
FastingProtocol,
|
|
Gender,
|
|
MealCategory,
|
|
MealPlanStatus,
|
|
Phase,
|
|
Prisma,
|
|
Role,
|
|
} from '@prisma/client';
|
|
export type {
|
|
Account,
|
|
FastEvent,
|
|
Ingredient,
|
|
MealPlan,
|
|
MealSlot,
|
|
Preferences,
|
|
Profile,
|
|
Recipe,
|
|
RecipeIngredient,
|
|
Session,
|
|
User,
|
|
Verification,
|
|
WeightEntry,
|
|
} from '@prisma/client';
|