mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-18 08:02:12 +00:00
perf(dashboard): split analytics fan-out across slim and thick queries
Pre-fix the dashboard fired a single `useAnalyticsQuery()` against the thick `/api/analytics` envelope. Every per-type tile on the dashboard strip waited on the heavy fan-out before paint. Mood and medication tiles arrived first (separate routes with their own dedicated 60 s LRU caches); every other tile then arrived as one delayed burst once the full slice landed. Marc reported the "blocked-then-burst" pattern as "etwas nervig" in the v1.4.39.1 post-deploy trace. The dashboard now mounts two `useAnalyticsQuery` calls in parallel: one for `?slice=summaries` (per-type tile strip + last-seen freshness map) and one for the thick envelope (BD-Zielbereich + glucose tiles). The tile strip paints as soon as the slim slice resolves; the BD-Zielbereich and glucose tiles stream in afterwards from the thick slice. TanStack's parallel-mounting keeps the network fan-out flat, and both queries share the `caches.analytics` 60 s LRU server-side so warm hits stay free. The `data` object the rest of the dashboard consumes stays shape- stable: a `useMemo` merges the two query results with slim winning on overlapping fields (slim and thick compute `summaries` / `lastSeenByType` from the same SQL helpers, so the values agree). The thick-only `bpInTargetPct*` and `glucoseByContext` fields read from the thick slice and surface as `null` / `undefined` until the thick query resolves; the BD-Zielbereich tile's data-floor gate already suppresses the tile cleanly in that interim state. A text-anchored test pins both query mounts so a future refactor cannot silently collapse the dashboard back onto the thick-only path.
This commit is contained in:
1 parent
f8a1319e94
commit
3126e4cff2
2 files changed
+102
-9
No files matched your search
@@ -0,0 +1,52 @@
|
||||
import { describe, it, expect } from "vitest";
|
||||
import { readFileSync } from "node:fs";
|
||||
import { join } from "node:path";
|
||||
|
||||
/**
|
||||
* v1.4.39.2 — dashboard analytics slim/thick split.
|
||||
*
|
||||
* Pre-fix the dashboard fired a single `useAnalyticsQuery()` against the
|
||||
* thick `/api/analytics` envelope; every per-type tile waited on the
|
||||
* heavy fan-out before paint. Mood and medication tiles arrived first
|
||||
* (separate routes) and then every other tile arrived as one burst,
|
||||
* which Marc reported as "etwas nervig" in the v1.4.39.1 post-deploy
|
||||
* trace.
|
||||
*
|
||||
* Post-fix the dashboard mounts TWO `useAnalyticsQuery` calls in
|
||||
* parallel: one for `?slice=summaries` (per-type tile strip) and one
|
||||
* for the thick envelope (BD-Zielbereich + glucose tiles). The tile
|
||||
* strip paints from the slim slice as soon as it lands; thick fields
|
||||
* stream in afterwards. Without this dual-mount the cold-mount UX
|
||||
* waterfall regresses to the v1.4.39.1 behaviour, so the test pins the
|
||||
* exact two call shapes.
|
||||
*/
|
||||
const ROOT = join(__dirname, "../../..");
|
||||
const PAGE_PATH = join(ROOT, "src/app/page.tsx");
|
||||
|
||||
function load(path: string): string {
|
||||
return readFileSync(path, "utf8");
|
||||
}
|
||||
|
||||
describe("v1.4.39.2 — dashboard analytics slim/thick split", () => {
|
||||
it("mounts both the slim slice and the thick slice in parallel", () => {
|
||||
const src = load(PAGE_PATH);
|
||||
// Slim slice — `?slice=summaries` paints the per-type tile strip.
|
||||
expect(src).toMatch(/useAnalyticsQuery\(\{\s*slice:\s*"summaries"\s*\}\)/);
|
||||
// Thick slice — the bare `useAnalyticsQuery()` (no slice) feeds
|
||||
// the BD-Zielbereich + glucose tiles. Both must coexist.
|
||||
expect(src).toMatch(/useAnalyticsQuery\(\)/);
|
||||
});
|
||||
|
||||
it("merges slim and thick results so call-sites stay shape-stable", () => {
|
||||
const src = load(PAGE_PATH);
|
||||
// The merge contract: slim wins on overlapping fields, thick fills
|
||||
// in `bpInTargetPct*` and `glucoseByContext`. The text anchors
|
||||
// protect against a future refactor accidentally dropping one of
|
||||
// the queries — the `data` object that downstream tile rendering
|
||||
// consumes must stay shape-stable across both query states.
|
||||
expect(src).toMatch(/analyticsSlimQuery/);
|
||||
expect(src).toMatch(/analyticsThickQuery/);
|
||||
expect(src).toMatch(/bpInTargetPct/);
|
||||
expect(src).toMatch(/glucoseByContext/);
|
||||
});
|
||||
});
|
||||
Reference in new issue
Block a user