From 7e6ed676e0fdfbd574e2df56a457b8215bd9a309 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marc-Andr=C3=A9=20Bombeck?= Date: Tue, 20 Oct 2026 11:03:18 +0200 Subject: [PATCH] docs(insights): describe the ECG section's failure row as it is The page comment still said the overview section unmounts silently on a read error; it shows a QueryErrorRow, which is what the UI standards ask of a supplementary block. The page keeps the full error card. --- src/app/insights/ecg/page.tsx | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/src/app/insights/ecg/page.tsx b/src/app/insights/ecg/page.tsx index 10cc0205a..7090cd437 100644 --- a/src/app/insights/ecg/page.tsx +++ b/src/app/insights/ecg/page.tsx @@ -41,9 +41,10 @@ export default function InsightsEcgPage() { const data = page?.data; // A read failure must be visible, not a heading over an empty body that - // reads the same as "still loading" (§6). The section teaser below unmounts - // silently on error, which is right for the overview but wrong for the page - // the user opened to see this list. + // reads the same as "still loading" (§6). The section shows a one-line + // `QueryErrorRow`, the right weight for a supplementary block on the + // overview; on the page the person opened to see this list the failure is + // the whole content, so it gets the full `QueryErrorCard` instead. if (isError) { return (