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 e95612e3d3 fix(sharing): show a guardian the controls the routes accept (#939 )

useRecordCapabilities answers per section now. canWriteDomain and
canManageDomain read the two lists the account payload publishes; in
one's own record they are always true, and under a refused, pending or
unproven context always false. canManage becomes the coarse switch,
true when any section is manageable, and is what the banner and the
navigation read.

Every add, edit and delete control names its own section: labs, mind,
profile, illness, cycle, medications, measurements, documents. Creates
that a WRITE route answers (visits, practitioners) ask canWriteDomain.
The generic delete button, the selection bar, the capture picker, the
dashboard quick entry and the bottom nav take the section from their
callers. Controls whose routes resolve the caller rather than the
record (settings shortcuts, chart overlay preferences, custom metrics,
the Today rail, OCR, efficacy targets, credential tabs) ask for the
caller's own record instead, and the customise-shortcut guard now
requires that shape.

The vault has no delegated write route, so its controls stay withheld
under every grant, and the documents page says so in one sentence
where the upload control would be, in all seven locales.

2026-09-09 19:42:27 +02:00

__tests__

fix(sharing): show a guardian the controls the routes accept (#939 )

2026-09-09 19:42:27 +02:00

app

fix(sharing): show a guardian the controls the routes accept (#939 )

2026-09-09 19:42:27 +02:00

cli

feat(mcp): add a local stdio MCP server for read-only health data

2026-06-27 13:25:53 +02:00

components

fix(sharing): show a guardian the controls the routes accept (#939 )

2026-09-09 19:42:27 +02:00

hooks

fix(sharing): show a guardian the controls the routes accept (#939 )

2026-09-09 19:42:27 +02:00

lib

feat(sharing): publish writable and manageable domains on the account payload

2026-09-09 19:42:26 +02:00

types

feat: surface a stalled or failed backup schedule

2026-09-03 02:22:37 +02:00

instrumentation.ts

fix(release): harden v1.31 arrival contracts

2026-07-20 00:40:20 +02:00

proxy.ts

feat(api): answer a retired route with 410 rather than a bare 404

2026-08-23 14:06:37 +02:00

README.md

refactor(openapi,queries): feature-located registries behind thin indexes

2026-06-11 00:10:00 +02:00

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.