mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-09 04:50:59 +00:00
Marc-André Bombeck
559366e308
Medications graduated from the always-on core set (weight / blood pressure / pulse stay core) to an opt-out module. The surface gates off the resolved module map — the left-nav entry, the dashboard medication widget, and the dedicated Medikamente settings entry hide when the account turns the module off. The medication data routes stay exempt from the gate (same data-layer reasoning as mood / labs): an importer, a sync, and the user's ability to clean up entries keep working while the surface is hidden, and re-enabling finds the schedule and intake history intact. Wire the module-route gate inventory, the dashboard widget/summary maps, the PATCH allowlist, and the nav model; regenerate the OpenAPI contract for the new module key.
51 lines
2.2 KiB
TypeScript
51 lines
2.2 KiB
TypeScript
/**
|
|
* v1.18.0 — module enable/disable request validation.
|
|
*
|
|
* The PATCH body is a partial map of TOGGLEABLE module keys → boolean.
|
|
* Only keys in the canonical registry (`MODULE_KEYS`) are accepted; a
|
|
* core-domain key (`weight`, `bloodPressure`, `pulse`) or any unknown key
|
|
* is a 422 — so the core measurement engine can never be disabled through
|
|
* this surface (defence-in-depth on top of the gate, which has no key to
|
|
* flip for core domains anyway). v1.18.1 (D3) — `medications` graduated to
|
|
* a toggleable module, so it IS writable here now.
|
|
*
|
|
* `strict()` rejects unknown keys outright rather than silently dropping
|
|
* them, so a client gets a clear error instead of a no-op.
|
|
*
|
|
* Delegated keys (`cycle`, `coach`) are NOT accepted here: their
|
|
* enabled-state is owned elsewhere (the cycle gate / `disableCoach` + the
|
|
* operator assistant flag), so a value for them would land inert in
|
|
* `modulePreferencesJson` and mislead — the Modules hub renders them as
|
|
* read-only "managed in X" rows that deep-link to the real control. Omitting
|
|
* them from the schema means a stale client sending `{ coach: false }` gets
|
|
* a clear 422 instead of a silent no-op behind a green "saved" toast.
|
|
*
|
|
* The shared shape is reused by the OpenAPI registry so the wire
|
|
* contract stays single-source.
|
|
*/
|
|
import { z } from "zod/v4";
|
|
|
|
import { MODULE_KEYS, moduleDelegatesTo } from "@/lib/modules/registry";
|
|
|
|
/**
|
|
* The directly-owned (non-delegated) toggleable keys — the only keys this
|
|
* PATCH surface may write into `modulePreferencesJson`.
|
|
*/
|
|
const WRITABLE_MODULE_KEYS = MODULE_KEYS.filter(
|
|
(k) => moduleDelegatesTo(k) === undefined,
|
|
);
|
|
|
|
/** Build `{ <writableKey>?: boolean }` from the directly-owned key list. */
|
|
const moduleShape = Object.fromEntries(
|
|
WRITABLE_MODULE_KEYS.map((k) => [k, z.boolean().optional()]),
|
|
) as Record<(typeof WRITABLE_MODULE_KEYS)[number], z.ZodOptional<z.ZodBoolean>>;
|
|
|
|
/**
|
|
* Partial module-preferences PATCH body. Every key is an optional
|
|
* boolean; omitted keys are left untouched server-side. `strict()`
|
|
* rejects any key not in `MODULE_KEYS` (including core domains).
|
|
*/
|
|
export const modulePrefsPatchSchema = z.object(moduleShape).strict();
|
|
|
|
export type ModulePrefsPatch = z.infer<typeof modulePrefsPatchSchema>;
|