Files
HealthLog/src/components/settings/integrations-section.tsx
T
Marc-André Bombeck 33d7d103da feat(settings): standardize settings and admin section framing
Introduce a shared SettingsSectionFrame (the settings twin of the admin
renderer's SectionFrame) that emits the canonical visible heading +
subheading, and route all 19 settings sections through it. Every settings
page now shows a real h1 + subtitle in the reference Übersicht style
instead of an invisible sr-only title; the section bodies drop their own
headings and off-style intro paragraphs (the explanatory copy folds into
the frame subtitle).

- Route the admin About page through SectionFrame so it carries the same
  visible heading as every other admin section.
- Rename the AI settings section from KI-Auswertung to KI-Anbieter across
  six locales: the page configures the provider and key, not an analysis.
- Add a heading-block spacer to the settings and admin sidebars so the
  first menu item lines up with the top of the first card.
- Remove the always-on core-domains card from Module: a tracking area that
  can't be turned off doesn't need listing.
- Move the proactive-coach control out of Benachrichtigungen into Coach.
- Move admin module availability out of the Coach section into its own
  page: it gates every module, not just the coach.
- Give the Layout Insights editor a proper Insights heading.

Adds settings.sections.<slug>.subtitle and the new admin keys across all
six locales; removes the now-unused module core-domain strings.
2026-06-18 21:28:33 +02:00

31 lines
1.2 KiB
TypeScript

"use client";
/**
* `<IntegrationsSection>` — Settings → Integrationen.
*
* v1.18.1 (D4) — the three sub-tabs (Connections / Channels / Sources) were
* split into three separate left-side settings entries. The Connections
* content IS the Integrationen page now: clicking Integrationen shows the
* OAuth + device data sources (Withings / WHOOP / Fitbit / Polar / Oura /
* Nightscout) directly, with no tab strip. Channels (delivery providers) and
* Sources (source weighting) each got their own entry — see
* `channels-section.tsx` and the standalone `sources` route.
*
* `parseOAuthOutcome` / `oauthReasonKey` are re-exported from
* `connections-panel.tsx` so existing unit-test imports keep resolving.
*/
import { ConnectionsPanel } from "@/components/settings/integrations/connections-panel";
export {
parseOAuthOutcome,
oauthReasonKey,
} from "@/components/settings/integrations/connections-panel";
export function IntegrationsSection() {
// v1.18.6 (W9) — the visible heading + subtitle and the module tour-replay
// trigger now live in the shared `<SettingsSectionFrame>` in the route; the
// body is the connections panel only.
return <ConnectionsPanel />;
}