tom/HealthLog

0 Fork 0

mirror of https://github.com/MBombeck/HealthLog.git synced 2026-11-08 12:32:43 +00:00

Files

T

Marc-André Bombeck 090e3d9a7e perf(measurements): weigh pulse days with window functions over one scan

The day weight joined its source to an hour grouping of itself. With
stale or missing planner statistics, as after a new account imports a
year of pulse below the autoanalyze threshold, the planner ran that
join as a nested loop and the all-time pulse aggregate ran into the
60 s statement timeout. The weight is now two window passes over one
scan: the readings in a row's hour, and one marker per hour summed over
the day for the hour count. The weights are unchanged.

A new integration test seeds over 100k pulse rows with autovacuum off
and no ANALYZE, bounds the all-time reader and a zoned per-source mean
well under the timeout, and compares every row's weight against the
earlier self-join after ANALYZE. The ANALYZE the metric-series snapshot
test needed for the same trap is gone.

2026-10-04 22:14:14 +02:00

__tests__

perf(backup): load the backup payload schema on first use

2026-10-04 18:23:14 +02:00

app

perf(backup): load the backup payload schema on first use

2026-10-04 18:23:14 +02:00

cli

…

components

Merge pull request #1144 from MBombeck/fix/restore-key-probe

2026-10-04 17:44:57 +02:00

hooks

feat(documents): read documents and lab scans in the background

2026-10-03 18:18:56 +02:00

lib

perf(measurements): weigh pulse days with window functions over one scan

2026-10-04 22:14:14 +02:00

types

fix(backup): notice a backup run the process died under, and take its account last

2026-10-04 15:56:56 +02:00

instrumentation.ts

feat(encryption): back up the key, and refuse to serve when it cannot open the database

2026-10-03 18:06:28 +02:00

proxy.ts

fix(monitoring): route Umami events to the endpoint the tracker was built with

2026-10-04 15:13:52 +02:00

README.md

…

README.md

`src/`

Application source. HealthLog is a Next.js 16 App Router project (output: "standalone", React 19, TypeScript strict). The path alias @/* resolves to this directory. Everything a request touches lives under here; the layout below follows the request flow rather than alphabetical order.

Request flow

client → src/proxy.ts → src/app/<route>/route.ts → src/lib/api-handler.ts → handler body → src/lib/api-response.ts → client

proxy.ts — the HTTP edge (Next.js 16's renamed middleware). Public-path allowlist, demo-mode mutation block, server-side onboarding redirect, worker-only refusal, x-request-id + CSP nonce generation, every security header.
app/ — App Router pages (RSC by default) and API routes. Every API route wraps its handler in apiHandler. See app/README.md.
lib/ — the server/runtime toolkit: apiHandler, auth, crypto, rollups, AI, notifications, pg-boss jobs, integrations, rate limiting. See lib/README.md.
components/ — React components (shadcn/ui new-york, kebab-case files). See components/README.md.

Other directories

hooks/ — shared React hooks (use- prefix, kebab-case).
types/ — shared TypeScript declarations.
generated/prisma/ — the generated Prisma client (do not edit; regenerated by prisma generate). Imported as @/generated/prisma.
instrumentation.ts — Next.js startup hook; boots the pg-boss worker registry and boot-time backfill queues.
__tests__/ — cross-cutting unit tests; most tests live in __tests__/ folders next to the code they cover.

Conventions

See ../CLAUDE.md for the full set. The load-bearing ones: RSC by default ("use client" only when a hook/state/browser API needs it); every API route wraps apiHandler and parses its body with Zod safeParse; userId is always narrowed from session or Bearer, never accepted as a body field; TanStack Query keys come only from src/lib/query-keys/; outbound HTTP goes through src/lib/safe-fetch.ts.