mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-09 04:50:59 +00:00
Marc-André Bombeck
058d1d7a69
/settings/mood manages the whole tag vocabulary: own groups (encrypted labels, twelve per account), custom tags with a searchable icon picker over a 75-icon catalog, hide and unhide of catalogue tags, archive semantics that never touch historical entries (hard delete only behind an explicit second confirm), and drag-or-arrow ordering of groups and tags shared by the picker. One GET serves the fully ordered tree — groups, placements, hidden and archived state — so the entry form, the settings section and a native client all read the same resolved layout. The picker finally renders custom tag labels (they were ignored since v1.13.0) and offers inline tag creation per group. The mood-tag API enters the OpenAPI contract for the first time, and the key-rotation script now covers both encrypted tag and group labels — custom tag labels had been missing from it since v1.13.0.
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).