import { env } from "../src/config/env.js";
import { prisma } from "../src/db/prisma.js";
import { syncRecipeSources } from "../src/db/recipe-source-sync.js";
import { seedReferenceData } from "../src/db/reference-seed-data.js";

/**
 * Refuses to run outside a database that's obviously a test one — belt and
 * braces alongside `config/env.ts` loading `.env.test` (not `.env`) under
 * `NODE_ENV=test`: this already wiped a real local dev database once, when
 * both env files shared one `DATABASE_URL`. `resetDatabase()` below
 * TRUNCATEs almost the entire schema before every single test, so a
 * misconfigured/missing `.env.test` must fail loudly here rather than
 * silently truncate whatever `DATABASE_URL` happens to be set.
 */
function assertRunningAgainstTestDatabase() {
  if (env.NODE_ENV !== "test") {
    throw new Error(
      `resetDatabase() TRUNCATEs almost the whole schema — refusing to run outside NODE_ENV=test (currently "${env.NODE_ENV}").`,
    );
  }
  // "test" covers a local `.env.test` (`batchcooking_test`); "ci" covers
  // CI's own service database (`batchcooking_ci`, set directly via the
  // workflow's `env:`, not a `.env.test` file — see ci.yml). Neither
  // matches the real dev database's name (`batchcooking`), which is the
  // one case this must actually catch.
  if (!env.DATABASE_URL?.includes("test") && !env.DATABASE_URL?.includes("ci")) {
    throw new Error(
      `resetDatabase() refuses to run against a DATABASE_URL that doesn't look like a test database (got "${env.DATABASE_URL}", expected it to contain "test" or "ci") — see .env.test.example.`,
    );
  }
}

// Single TRUNCATE ... CASCADE covers FK ordering and resets identity
// sequences — used between tests/scenarios to start from a clean slate.
// Re-seeds the Diet/Category/Allergy/Unit reference data right after
// truncating it, so every test starts from the same realistic reference
// data the real app seeds (`prisma/seed.ts`) rather than empty tables —
// tests exercising dietId/allergyIds/unitId need real rows to reference.
// `syncRecipeSources` runs last, for the same reason: `sources` should
// reflect whatever adapters this test run happens to have registered
// (usually none — see recipe-source-registry.ts).
export async function resetDatabase() {
  assertRunningAgainstTestDatabase();
  await prisma.$executeRawUnsafe(`
    TRUNCATE TABLE
      "user_profile_allergy", "user_preference", "allergy", "category",
      "planning_item", "planning",
      "recipe_ingredient", "step_tech_step", "step", "tech_step",
      "recipe", "ingredients", "sources", "unit",
      "user_profiles", "diet", "house",
      "admin_users", "analytics_events", "worker_heartbeats"
    RESTART IDENTITY CASCADE;
  `);
  await seedReferenceData(prisma);
  await syncRecipeSources(prisma);
}
