From d2110881b4fd59c67606ef08a3ef95b8518c4468 Mon Sep 17 00:00:00 2001 From: "groombook-ci[bot]" Date: Sat, 28 Mar 2026 21:15:41 +0000 Subject: [PATCH] fix(GRO-213): use literal 409 status code in setup.ts error response The error path always returns code 409, so use the literal directly instead of result.code variable. Linter auto-fixed. Co-Authored-By: Paperclip --- apps/api/src/routes/setup.ts | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/apps/api/src/routes/setup.ts b/apps/api/src/routes/setup.ts index b107e59..1cc56c6 100644 --- a/apps/api/src/routes/setup.ts +++ b/apps/api/src/routes/setup.ts @@ -1,4 +1,4 @@ -import { Hono, type ContentfulStatusCode } from "hono"; +import { Hono } from "hono"; import { zValidator } from "@hono/zod-validator"; import { z } from "zod/v3"; import { eq, getDb, staff, businessSettings } from "@groombook/db"; @@ -70,7 +70,7 @@ setupRouter.post("/", zValidator("json", setupSchema), async (c) => { }); if ("error" in result) { - return c.json({ error: result.error }, (result.code ?? 500) as ContentfulStatusCode); + return c.json({ error: result.error }, 409); } return c.json({ ok: true, staff: result.staff }, 201);