mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-08 04:32:42 +00:00
Marc-André Bombeck
4038a34ae6
The page-scoped selection bar sat sticky bottom-2, behind the fixed 64px mobile bottom-nav, so the destructive Delete (N) button was unreachable on phones and ignored the iOS home-indicator inset. Lift it to clear the nav band + safe area on mobile and drop back to bottom-4 at sm+ where the nav is hidden. The per-row select checkbox wrapped a Radix checkbox (a 16px button) in a 44px label; a label does not forward taps to a button, so the effective target failed WCAG 2.5.5. Make the 44px area a single button that owns the toggle, with the checkbox a pointer-events-none controlled visual, avoiding any double-toggle. Bring the mood pagination buttons to the 44px target used by the measurements list. Add (sort: Desc) to the two source-filter indexes so the schema matches the DESC migration SQL; schema-fidelity only, no new migration.
prisma/
The database layer. HealthLog runs PostgreSQL 16 via Prisma 7. This directory holds the single schema file and the forward-only migration history; the generated client is emitted elsewhere.
Contents
schema.prisma— 61 models, one file.cuid()primary keys,snake_casecolumns via@map(...), encrypted columns mostly suffixed*Encrypted(search the file; there are 24 encrypted column references). Thegenerator clientblock emits to../src/generated/prisma(imported as@/generated/prisma).migrations/— numbered, forward-only SQL migrations (0001_…upward).migration_lock.tomlpins the provider topostgresql.
Migration workflow
# author a migration from a schema edit
pnpm dlx prisma migrate dev --name <short_snake_case_name>
# regenerate the client after any schema change
pnpm dlx prisma generate
Number a new migration with the next free prefix. The production entrypoint runs prisma migrate deploy on boot, so every migration must apply cleanly forward — there is no down-migration path. Always include the migration file in the same change as the schema edit.
Conventions
- Encryption is fail-closed:
*Encryptedcolumns are written through@/lib/crypto(AES-256-GCM, versioned key ids); never store plaintext in an encrypted column. Key rotation isscripts/rotate-encryption-key.ts+docs/ops/encryption-key-rotation.md. - The generated client under
src/generated/prismais build output — do not edit it. - Schema-touching changes that affect the API surface must regenerate
docs/api/openapi.yaml(see../CLAUDE.md).
Related: ../src/lib/README.md (db.ts, rollups/), ../docs/ops/ (migrations + backup runbooks).