Files
HealthLog/src/components/settings/integrations-section.tsx
T
Marc-André Bombeck 11774f731e refactor(settings): fold tracking modules into Appearance, dedupe nav
Collapse the duplicated settings navigation so each surface lives in
one place:

- Appearance ("Darstellung") stops being a link hub and renders the
  dashboard, insights, and every tracking module's settings inline as
  stacked, anchored sections. Each module section keeps its module
  gate, so a disabled module's section does not render. The standalone
  Medikamente / Stimmung / Labor / Krankheit / Vorsorge nav entries are
  gone; their routes 301-redirect to /settings/layout#<anchor>.
- Move the delivery channels out of Notifications into Integrations,
  where the other connected services live. Notifications keeps only the
  reminder types. /settings/channels now redirects to
  /settings/integrations#channels; the per-channel anchors still resolve.
- Fold the clinician share-link surface into the health-record section
  as a labelled Sharing group. /settings/sharing redirects to
  /settings/gesundheitsakte#sharing.
- Drop the duplicated active-sessions and security-activity cards from
  Account; they remain under Data & Privacy.
- Reserve the scrollbar gutter on the settings content column so a
  section with a vertical scrollbar and one without render at the same
  width.

Move-only: every card renders through its existing component unchanged.
2026-06-29 22:16:02 +02:00

61 lines
2.5 KiB
TypeScript

"use client";
/**
* `<IntegrationsSection>` — Settings → Integrationen.
*
* v1.18.1 (D4) — the Connections content IS the Integrationen page: clicking
* Integrationen shows the OAuth + device data sources (Withings / WHOOP /
* Fitbit / Polar / Oura / Nightscout) directly, with no tab strip.
*
* v1.25.7 — the delivery CHANNELS (Telegram / ntfy / Web Push / Webhook /
* Email) move back here from Notifications as a labelled "Delivery channels"
* group below the connections. Channels are delivery providers — the same
* conceptual family as Withings / WHOOP / a connected device — not reminder
* preferences, so they belong with the other integrations. Notifications keeps
* only the reminder-TYPE content. The group carries `id="channels"` so
* `/settings/channels` 301-redirects to `/settings/integrations#channels`, and
* the per-channel anchors (`#telegram`, `#ntfy`, …) inside the panel keep
* working.
*
* `parseOAuthOutcome` / `oauthReasonKey` are re-exported from
* `connections-panel.tsx` so existing unit-test imports keep resolving.
*/
import { useTranslations } from "@/lib/i18n/context";
import { ConnectionsPanel } from "@/components/settings/integrations/connections-panel";
import { NotificationChannelsPanel } from "@/components/settings/integrations/notification-channels-panel";
export {
parseOAuthOutcome,
oauthReasonKey,
} from "@/components/settings/integrations/connections-panel";
export function IntegrationsSection() {
const { t } = useTranslations();
// v1.18.6 (W9) — the visible page heading + subtitle come from the shared
// `<SettingsSectionFrame>` in the route; the connections panel is the
// primary surface, with the delivery-channels group sequenced below it.
return (
<div className="space-y-10">
<ConnectionsPanel />
{/* Delivery channels ("where it's delivered"). The existing channels
panel, unchanged. `id="channels"` anchors the group for the
`/settings/channels` redirect; the per-channel anchors stay inside
the panel. */}
<section id="channels" className="scroll-mt-28 space-y-4">
<div className="space-y-0.5">
<h2 className="text-foreground text-lg font-semibold">
{t("settings.sections.integrations.channelsHeading")}
</h2>
<p className="text-muted-foreground text-sm">
{t("settings.sections.integrations.channelsDescription")}
</p>
</div>
<NotificationChannelsPanel />
</section>
</div>
);
}