"use client"; /** * v1.17.1 — shared "Setup guide" doc-link for every Settings → Integrations * card. Each card paints the same affordance: one discreet, external link to * the provider's setup runbook ("was eingeben, wo klicken"). Single-sourced * here so all six cards (WHOOP / Withings / Fitbit / Polar / Oura / Nightscout) * read as one family and the docs host lives in exactly one place. * * The runbooks themselves are authored separately; this link wires the * destination now so a user who is mid-setup always knows where to go. */ import { useSyncExternalStore } from "react"; import { ExternalLink } from "lucide-react"; import { useTranslations } from "@/lib/i18n/context"; /** * Base for every provider setup runbook. The provider key is appended as a * path segment, e.g. `https://docs.healthlog.dev/integrations/whoop`. Kept as * a single constant so the host never drifts across cards. */ export const INTEGRATION_DOCS_BASE = "https://docs.healthlog.dev/integrations"; export type IntegrationDocsProvider = | "whoop" | "withings" | "fitbit" | "polar" | "oura" | "nightscout" // v1.27.0 — Google Health runbook (docs.healthlog.dev/integrations/google-health). | "google-health" // v1.28.x — Strava runbook (docs.healthlog.dev/integrations/strava). | "strava"; export function integrationDocsHref(provider: IntegrationDocsProvider): string { return `${INTEGRATION_DOCS_BASE}/${provider}`; } /** * Shows a compact warning when the callback origin differs from the app. * * `callbackUrl` is the value the server registers as `redirect_uri`, resolved * per request by `getIntegrationCallbackUrls()` and passed down as a prop. It * must not be derived here: a `NEXT_PUBLIC_*` read in a client module is * inlined at build time, and the published image is built without it. * `null` means the provider cannot build a redirect URI from the current env, * so there is nothing to compare. */ export function CallbackMismatchNotice({ provider, callbackUrl, }: { provider: string; callbackUrl: string | null; }) { // Get the current origin of the app const { t } = useTranslations(); const currentOrigin = useSyncExternalStore( () => () => {}, () => window.location.origin, () => null, ); // Get the origin of the callback URL const callbackOrigin = (() => { if (!callbackUrl) return null; try { return new URL(callbackUrl).origin; } catch { return null; } })(); if (!currentOrigin || !callbackOrigin || callbackOrigin === currentOrigin) { return null; } // If the callback origin differs from the app, show a warning return ( {t("settings.oauthCallbackPreflightItem", { provider, configuredOrigin: callbackOrigin, currentOrigin, })} ); } /** * v1.29.x (UX audit H2) — compact 3-step BYO-developer-app guide for the * six providers that require a self-hoster to register their own vendor * app before an OAuth connect can ever succeed (Withings / WHOOP / Fitbit / * Polar / Oura / Strava). The external "Setup guide" link explains the * *why*; this inline callout gives the one value every vendor form asks * for and the app already knows — the callback URL — so it doesn't have to * be reconstructed by hand from the docs. Shown only while the user hasn't * saved their own credentials yet; it steps out of the way once configured. */ export function IntegrationRedirectGuide({ provider, providerLabel, callbackUrl, }: { provider: IntegrationDocsProvider; providerLabel: string; /** * The server-resolved callback URL (see `CallbackMismatchNotice`). When the * provider cannot build one from the current env, show the fixed path so * the step still names what the vendor form expects. */ callbackUrl: string | null; }) { const { t } = useTranslations(); const shownCallbackUrl = callbackUrl ?? `/api/${provider}/callback`; return (

{t("settings.integrationRedirectGuide.intro", { provider: providerLabel, })}

  1. {t("settings.integrationRedirectGuide.step1", { provider: providerLabel, })}
  2. {t("settings.integrationRedirectGuide.step2")}{" "} {shownCallbackUrl}
  3. {t("settings.integrationRedirectGuide.step3")}
); } /** * The one description every integration card paints: ONE sentence, then the * setup-guide link inline at the end of it. * * It used to be two paragraphs stacked in the description slot — a white * primary sentence and a grey secondary one whose only job was to carry the * link. The secondary sentence was byte-identical across six of the eight * cards, which is the tell: it said nothing about the provider it sat under. * The link is the part that carried information, so the link is what stayed. */ export function IntegrationCardDescription({ i18nPrefix, provider, }: { i18nPrefix: string; provider: IntegrationDocsProvider; }) { const { t } = useTranslations(); return ( <> {t(`${i18nPrefix}Description`)}{" "} {t("settings.integrationSetupGuide")} ); }