mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-07 04:12:04 +00:00
Marc-André Bombeck
c86c7d1a79
Add the in-repo rule `healthlog/import-boundaries`: - a file under src/lib may not import src/components or src/app (alias, relative, re-export and dynamic forms, type-only included); - a "use client" file may not make a value import of the database client, the crypto module, the Prisma client entry, the job queue, pg, pg-boss or next/headers. Type-only imports and the Prisma enums entry stay legal. The four lib files that still import upward are listed in the rule's allow map with a reason each; a listed file that stops importing upward is reported, so the map can only shrink. Five of the nine upward imports are gone by moving pure modules to their layer, without behaviour change: - supply-runway estimate → src/lib/medications/supply-runway.ts (read by the low-stock job and the medication list read); - weekday BYDAY tokens → src/lib/medications/scheduling/weekday-tokens.ts (read by the medication extraction prompt); - settings section slugs → src/lib/settings/section-slugs.ts (read by the record-settings classification); - the command palette index → src/components/command-palette/ (it is a client index built from component registries). Proof the rule can fail: an import of @/components/ui/card appended to src/lib/medications/supply-runway.ts reported libUpward, and a planted "use client" file importing @/lib/db reported clientServerOnly; both were removed again.
131 lines
7.2 KiB
TypeScript
131 lines
7.2 KiB
TypeScript
/**
|
|
* Server-safe constants for the v1.4 settings split. Kept in a separate
|
|
* module from `<SettingsShell>` (a client component) so server-rendered code
|
|
* paths — `generateStaticParams()`, the page guard, future tests — can import
|
|
* the slug list without dragging the whole client bundle into the server
|
|
* graph.
|
|
*/
|
|
|
|
// v1.18.0 — `sources` was folded into Settings → Integrations as the
|
|
// "Sources" sub-tab.
|
|
// v1.18.1 — the Integrations sub-tabs (Connections / Channels / Sources)
|
|
// were split back into three separate left-side entries: `integrations` (the
|
|
// Connections content, shown directly), `channels` (delivery channels), and
|
|
// `sources` (source weighting). The `/settings/sources` redirect is gone
|
|
// (it is a real route again); `channels` is a brand-new entry.
|
|
// `thresholds` (Targets) keeps its own left-nav entry + route, served by the
|
|
// dynamic `[section]` route below.
|
|
// v1.16.10 — `medications` sits after `insights`: the customise surface
|
|
// for the /medications list (view preference + manual order), following
|
|
// the dashboard / insights pattern of a dedicated settings section
|
|
// reached from the page header's Settings2 glyph.
|
|
// v1.17 — `mood` sits after `medications`: the mood-tag management
|
|
// surface (groups, custom tags, hide/archive, picker order), reached
|
|
// from the /mood page header's wrench glyph.
|
|
// v1.18.7 — `labs`, `illness`, and `vorsorge` move INTO the Settings
|
|
// shell as first-class sections, right after `mood`, so the three
|
|
// tracking-domain customise surfaces sit together. They were standalone
|
|
// `ModuleSettingsFrame` pages (their own back-button + title, outside the
|
|
// shell); now the dynamic `[section]` route renders them in shell chrome
|
|
// 1:1 with the other sections. The wrench deep-links (`/settings/labs`,
|
|
// `/settings/illness`, `/settings/vorsorge`) are unchanged — they now
|
|
// resolve through the shell. `labs` + `illness` are module-gated (they are
|
|
// toggleable modules); `vorsorge` (preventive-care reminders) is not a
|
|
// module, so its entry is always shown.
|
|
// v1.17.1 — `layout` is the one "Layout & Personalization" home.
|
|
// The dashboard / insights / medications / mood personalization editors
|
|
// each keep their own route (deep links, page-header cogs, and the hub's
|
|
// own links all resolve), but the settings NAV now surfaces a single
|
|
// `layout` entry instead of four scattered "arrange" entries, so the
|
|
// concept reads as one place. The four editor slugs stay in this list so
|
|
// their routes still resolve; they are simply not listed in the shell nav.
|
|
// v1.18.0 — the standalone `reminders` hub is gone. It was a
|
|
// link-only page ("doppelt gemoppelt") that merely deep-linked into the
|
|
// canonical editors; reminder TYPES now live centrally in `notifications`,
|
|
// each row gated on its module. `/settings/reminders` 301-redirects to
|
|
// `/settings/notifications` (next.config.ts).
|
|
// v1.18.0 — per-submodule settings split. `gesundheitsakte` (the full
|
|
// health-record export, always available) lifts out of Export & Import into
|
|
// its own top-level entry.
|
|
export const SETTINGS_SECTION_SLUGS = [
|
|
"account",
|
|
// v1.23 — `security` is the dedicated account-security home: second-factor
|
|
// setup (TOTP + security keys), recovery codes, and passkey management. Sits
|
|
// right after `account` so the two identity surfaces read as neighbours.
|
|
"security",
|
|
// v1.36.0 — `access` ("Shared access"): which other accounts on this
|
|
// instance may open this health record, which records this one may open, and
|
|
// when they were opened. Sits beside `security` because it answers the same
|
|
// question those surfaces do — who can get at my account, and what have they
|
|
// been doing. Distinct from the `sharing` slug below, which is the clinician
|
|
// share LINK (a time-boxed read-only report handed to somebody outside the
|
|
// instance); this one is a standing relationship between two accounts on it.
|
|
"access",
|
|
// v1.18.0 — `modules` ("Was du trackst") sits right after account: the
|
|
// single front door for enabling/disabling secondary tracking domains.
|
|
"modules",
|
|
"integrations",
|
|
// v1.18.1 — Quellen (source weighting) split out of the Integrations
|
|
// tabs into its own left-side entry. v1.25.3 — Kanäle (delivery channels)
|
|
// folded back into Notifications as an in-page group; `/settings/channels`
|
|
// 301-redirects to `/settings/notifications#channels` (next.config.ts).
|
|
"sources",
|
|
"notifications",
|
|
// v1.37.19 — the per-module personalization slugs (`dashboard`,
|
|
// `insights`, `medications`, `mood`, `labs`, `illness`, `vorsorge`) and
|
|
// `sharing` left this list. Their URLs are owned by permanent redirects
|
|
// in `next.config.ts` (`/settings/<module>` → `/settings/layout/<module>`,
|
|
// `/settings/sharing` → `/settings/gesundheitsakte#sharing`), so the
|
|
// dynamic route could never serve them — prerendering eight unreachable
|
|
// pages and keeping eight dead component wirings. The redirects, the
|
|
// section components, and the layout-hub subpages are unchanged.
|
|
"layout",
|
|
// v1.25 — "Umwelt" (environmental context): home location, travel
|
|
// overrides, and the weather/daylight backfill. Module-gated on the opt-in
|
|
// `environment` module (the nav entry only shows when it is on).
|
|
"environment",
|
|
// v1.25 — "Anamnese" (medical history): the structured-record
|
|
// home for allergies + family history. Always shown (not module-gated, like
|
|
// `vorsorge`); the records are foundational health-profile data.
|
|
"anamnesis",
|
|
// v1.35.0 — "Health Score": which pillars count toward the composite.
|
|
// Its own surface rather than a corner of the modules hub, because the
|
|
// module switches answer a different question (what is recorded and
|
|
// shown) and folding the two together is what kept the score's
|
|
// composition invisible.
|
|
"score",
|
|
"thresholds",
|
|
"ai",
|
|
// v1.18.0 — `coach` gathers the Coach preference cards (disable
|
|
// toggle, preferences, memory) out of the AI section, module-gated on
|
|
// the coach module. The `ai` entry keeps provider / model / BYOK only.
|
|
"coach",
|
|
"api",
|
|
// v1.22.0 — the remote MCP connector card: enable the opt-in `mcp` module and
|
|
// mint / revoke the dedicated `health:read` token used to connect an external
|
|
// assistant (Claude.ai / ChatGPT). Sits next to `api` (both are programmatic
|
|
// access surfaces). Not nav-gated — the card carries its own enable toggle.
|
|
"mcp",
|
|
"gesundheitsakte",
|
|
"export",
|
|
"advanced",
|
|
// v1.23 — "Data & Privacy": a single surface that assembles the already-
|
|
// shipped export / deletion / retention / encryption / session / activity
|
|
// pieces into one coherent privacy pane. Sits next to `advanced` (the
|
|
// destructive-action home) and before `about`.
|
|
"privacy",
|
|
// v1.44 — "Preview features" (per-user opt-ins, Settings > System) is not
|
|
// listed until the first preview it switches, the topic pages, ships: a
|
|
// switch that changes nothing is a promise the page cannot keep. The stored
|
|
// flag, `/api/settings/preview-features` and its backup round-trip stay.
|
|
"about",
|
|
] as const;
|
|
|
|
export type SettingsSectionSlug = (typeof SETTINGS_SECTION_SLUGS)[number];
|
|
|
|
export function isSettingsSectionSlug(
|
|
value: string,
|
|
): value is SettingsSectionSlug {
|
|
return (SETTINGS_SECTION_SLUGS as readonly string[]).includes(value);
|
|
}
|