TopDogLabs/gantt-board
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Signed-off-by: Max <ai-agent@topdoglabs.com>

Browse Source
This commit is contained in:
Max 2026-02-22 14:55:28 -06:00
parent 29cac07f58
commit eba669f187
3 changed files with 15 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -39,6 +39,12 @@ Task and sprint board built with Next.js + Zustand and Supabase-backed API persi
- Accepts date strings with a `YYYY-MM-DD` prefix (`YYYY-MM-DD` or ISO timestamp). - Accepts date strings with a `YYYY-MM-DD` prefix (`YYYY-MM-DD` or ISO timestamp).
- Normalizes and persists only the date part (`YYYY-MM-DD`). - Normalizes and persists only the date part (`YYYY-MM-DD`).
- `PATCH` returns `400` for invalid `startDate`/`endDate` format. - `PATCH` returns `400` for invalid `startDate`/`endDate` format.
- Example request payloads:
- `POST /api/sprints`
- `{ "name": "Sprint 1", "startDate": "2026-02-16", "endDate": "2026-02-22", "status": "active", "projectId": "<uuid>" }`
- `PATCH /api/sprints`
- `{ "id": "<sprint-id>", "startDate": "2026-02-16T00:00:00.000Z", "endDate": "2026-02-22T23:59:59.999Z" }`
- persisted as `start_date = '2026-02-16'`, `end_date = '2026-02-22'`
- Do not use `new Date("YYYY-MM-DD")` for sprint display logic. Use shared helpers: - Do not use `new Date("YYYY-MM-DD")` for sprint display logic. Use shared helpers:
- `parseSprintStart(...)` - `parseSprintStart(...)`
- `parseSprintEnd(...)` - `parseSprintEnd(...)`

6
SUPABASE_SETUP.md
View File

@ -133,6 +133,12 @@ Or push to git and let Vercel auto-deploy.
- API behavior: - API behavior:
- `/api/sprints` normalizes `startDate` and `endDate` to `YYYY-MM-DD` before persistence. - `/api/sprints` normalizes `startDate` and `endDate` to `YYYY-MM-DD` before persistence.
- Invalid date format on `PATCH /api/sprints` returns `400`. - Invalid date format on `PATCH /api/sprints` returns `400`.
- API payload examples:
- `POST /api/sprints`
- `{ "name": "Sprint 1", "startDate": "2026-02-16", "endDate": "2026-02-22", "status": "active", "projectId": "<uuid>" }`
- `PATCH /api/sprints`
- `{ "id": "<sprint-id>", "startDate": "2026-02-16T00:00:00.000Z", "endDate": "2026-02-22T23:59:59.999Z" }`
- stored as date-only values in Supabase `DATE` columns
## Architecture Changes ## Architecture Changes

4
src/app/api/sprints/route.ts
View File

@ -4,6 +4,8 @@ import { getAuthenticatedUser } from "@/lib/server/auth";
export const runtime = "nodejs"; export const runtime = "nodejs";
// Sprint dates are stored as SQL DATE values (YYYY-MM-DD). We accept either
// date-only or ISO datetime inputs and normalize to the date prefix.
const DATE_PREFIX_PATTERN = /^(\d{4}-\d{2}-\d{2})/; const DATE_PREFIX_PATTERN = /^(\d{4}-\d{2}-\d{2})/;
function toDateOnlyInput(value: unknown): string | null { function toDateOnlyInput(value: unknown): string | null {
@ -114,7 +116,7 @@ export async function PATCH(request: Request) {
const supabase = getServiceSupabase(); const supabase = getServiceSupabase();
const now = new Date().toISOString(); const now = new Date().toISOString();
// Map camelCase to snake_case for database // Map camelCase to snake_case for database and keep date-only semantics.
const dbUpdates: Record<string, unknown> = {}; const dbUpdates: Record<string, unknown> = {};
if (updates.name !== undefined) dbUpdates.name = updates.name; if (updates.name !== undefined) dbUpdates.name = updates.name;
if (updates.goal !== undefined) dbUpdates.goal = updates.goal; if (updates.goal !== undefined) dbUpdates.goal = updates.goal;