mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-13 06:32:03 +00:00
Marc-André Bombeck
ec82ad3a93
The getting-started checklist reads the answers: a visit named within a month adds a "prepare the visit" row that is done once one is on the calendar, and the data-source row names the wearable that was chosen. Its per-browser state moves to one module so the done screen, the skip and Settings write the same keys. Settings → Account gains the two ways back in: "Set up again" through the restart route, which resets the ledger, keeps the answers as prefill and touches no module; and "Show the checklist again", which forgets what this browser hid. A page whose module is off now answers with the shared notice and the one action that helps, in one place for every module page: the shell maps the route to the module through the navigation model's own gate, so a page and its nav entry cannot disagree about which switch they follow. And the tour's two dead stops get their anchors on the integrations and health-record group headings.
106 lines
4.7 KiB
TypeScript
106 lines
4.7 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.
|
|
*
|
|
* 2026-07-17 UX/IA audit M7 — `<NutrientIntakeCard>` (v1.28) moved here from
|
|
* Settings → Sources. It is a read-only sync inventory (what the Apple
|
|
* Health nutrients opt-in has stored), not a which-connection-wins ranking —
|
|
* "Source priority" describes the latter only. Matches the standing
|
|
* providers→Integrations rule; the card still renders nothing while the
|
|
* `nutrients` module is off.
|
|
*/
|
|
|
|
import Link from "next/link";
|
|
import { Link2, Send } from "lucide-react";
|
|
|
|
import { useTranslations } from "@/lib/i18n/context";
|
|
import type { IntegrationCallbackUrls } from "@/lib/integrations/callback-urls";
|
|
import { ConnectionsPanel } from "@/components/settings/integrations/connections-panel";
|
|
import { SectionHeading } from "@/components/ui/section-heading";
|
|
import { NotificationChannelsPanel } from "@/components/settings/integrations/notification-channels-panel";
|
|
import { NutrientIntakeCard } from "@/components/settings/nutrient-intake-card";
|
|
import { Button } from "@/components/ui/button";
|
|
|
|
export {
|
|
parseOAuthOutcome,
|
|
oauthReasonKey,
|
|
} from "@/components/settings/integrations/connections-panel";
|
|
|
|
export function IntegrationsSection({
|
|
callbackUrls,
|
|
}: {
|
|
/** Server-resolved per-provider OAuth callback URLs; see `ConnectionsPanel`. */
|
|
callbackUrls: IntegrationCallbackUrls;
|
|
}) {
|
|
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">
|
|
{/* Connections ("where the data comes from"). The OAuth + device data
|
|
sources. A labelled group header gives this block parity with the
|
|
delivery-channels group below it. */}
|
|
<section className="space-y-4">
|
|
<SectionHeading
|
|
icon={Link2}
|
|
title={t("settings.sections.integrations.connectionsHeading")}
|
|
// The module tour's "integrations" stop anchors here.
|
|
tourId="integrations-hero"
|
|
/>
|
|
<ConnectionsPanel callbackUrls={callbackUrls} />
|
|
|
|
{/* 2026-07-17 UX/IA audit M7 — the opt-in nutrients sync inventory
|
|
(moved from Settings → Sources, where "source priority" only
|
|
ever meant which-connection-wins ranking, not a read-only sync
|
|
list). The card carries its own header + renders nothing while
|
|
the `nutrients` module is off, so it slots in as a sibling card
|
|
under the same Connections group rather than a new labelled
|
|
section that could paint an orphaned heading over nothing. */}
|
|
<NutrientIntakeCard />
|
|
</section>
|
|
|
|
{/* 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">
|
|
<SectionHeading
|
|
icon={Send}
|
|
title={t("settings.sections.integrations.channelsHeading")}
|
|
subtitle={t("settings.sections.integrations.channelsDescription")}
|
|
/>
|
|
{/* Names the per-event notification matrix so the three notification
|
|
surfaces (matrix, reminder types, channels) cross-reference. */}
|
|
<div>
|
|
<Button asChild variant="outline" size="sm">
|
|
<Link href="/notifications">
|
|
{t("settings.sections.integrations.matrixLink")}
|
|
</Link>
|
|
</Button>
|
|
</div>
|
|
<NotificationChannelsPanel />
|
|
</section>
|
|
</div>
|
|
);
|
|
}
|