mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-15 23:12:04 +00:00
Server and first client render now agree everywhere query state used to leak into the chrome, checkboxes no longer nest inside buttons, delete confirmations admit the undo they offer, raw step counts drop their decimals, the truncated unit label wraps instead, streaks know their singular, the medication header speaks the user's date format, a failed coach turn keeps the user's message and says what went wrong, settings status notes follow a language switch, the locale only flips once its bundle actually loaded, and the last raw api fetches in hooks move onto the shared client.
55 lines
2.0 KiB
TypeScript
55 lines
2.0 KiB
TypeScript
"use client";
|
|
|
|
import { useQuery } from "@tanstack/react-query";
|
|
|
|
import { queryKeys } from "@/lib/query-keys";
|
|
import { apiGet } from "@/lib/api/api-fetch";
|
|
import {
|
|
DEFAULT_INSIGHTS_LAYOUT,
|
|
resolveInsightsLayout,
|
|
type InsightsLayout,
|
|
} from "@/lib/insights-layout";
|
|
|
|
/**
|
|
* v1.15.11 — the resolved insights overview layout (sections + tiles) plus the
|
|
* query load status.
|
|
*
|
|
* Reads `GET /api/insights/layout` through the centralised query-key factory
|
|
* (`queryKeys.insightsLayout()` → `["user","insightsLayout"]`), the same key
|
|
* the inline-edit PUT mutation invalidates on save so the overview repaints in
|
|
* lockstep with the edit surface. The response is already the server-resolved
|
|
* v2 layout; we pass it back through `resolveInsightsLayout` defensively so a
|
|
* partial / legacy blob from a stale cache still normalises to a valid
|
|
* `InsightsLayout`.
|
|
*
|
|
* Returns `DEFAULT_INSIGHTS_LAYOUT` while the query is in-flight so the page
|
|
* renders in the default section + tile order on first paint — no layout
|
|
* flicker, no empty state, no "everything hidden" flash before the saved
|
|
* layout lands.
|
|
*
|
|
* `isLoading` lets a caller gate a write surface (the inline "Anpassen" edit
|
|
* mode) until the GET has settled: without that gate a user who enters edit
|
|
* mode while the layout is still in-flight would seed the editor from
|
|
* `DEFAULT_INSIGHTS_LAYOUT` and a "Fertig" save would PUT defaults over their
|
|
* real saved layout.
|
|
*/
|
|
export function useInsightsLayoutQuery(enabled: boolean): {
|
|
layout: InsightsLayout;
|
|
isLoading: boolean;
|
|
isSuccess: boolean;
|
|
} {
|
|
const { data, isLoading, isSuccess } = useQuery({
|
|
queryKey: queryKeys.insightsLayout(),
|
|
queryFn: async () =>
|
|
resolveInsightsLayout(await apiGet("/api/insights/layout")),
|
|
enabled,
|
|
});
|
|
return {
|
|
layout: data ?? DEFAULT_INSIGHTS_LAYOUT,
|
|
// `enabled: false` keeps the query in a pending-but-idle state; treat a
|
|
// disabled (unauthenticated) query as not-loading so the gate never sticks.
|
|
isLoading: enabled && isLoading,
|
|
isSuccess,
|
|
};
|
|
}
|