75b3c94f60
ci / rust (push) Failing after 45s
ci / web (push) Successful in 52s
docker / build-push (--build-arg FEDORA_VERSION=44, ci, ci/fedora-rpm.Dockerfile, punktfunk-fedora44-rpm) (push) Successful in 10s
ci / docs-site (push) Successful in 1m6s
decky / build-publish (push) Successful in 33s
docker / build-push (., web/Dockerfile, punktfunk-web) (push) Successful in 30s
docker / build-push (docs-site, docs-site/Dockerfile, punktfunk-docs) (push) Successful in 10s
ci / bench (push) Successful in 6m1s
docker / build-push (ci, ci/rust-ci.Dockerfile, punktfunk-rust-ci) (push) Successful in 8m33s
docker / build-push (ci, ci/fedora-rpm.Dockerfile, punktfunk-fedora-rpm) (push) Successful in 9m40s
docker / deploy-docs (push) Successful in 26s
windows-host / package (push) Successful in 15m34s
rpm / build-publish (44, fedora-44, punktfunk-fedora44-rpm) (push) Successful in 13m24s
arch / build-publish (push) Successful in 20m32s
android / android (push) Successful in 20m50s
deb / build-publish (push) Successful in 20m33s
rpm / build-publish (43, bazzite, punktfunk-fedora-rpm) (push) Successful in 21m41s
apple / swift (push) Has been cancelled
apple / screenshots (push) Has been cancelled
Pairing: - Refresh the paired-devices list after a native PIN pairing (the happy path never invalidated it, so a newly paired device stayed hidden until remount). - Moonlight PIN: a 204 means "PIN delivered to the waiting handshake", NOT paired, so it now reads "PIN sent" instead of a false "Paired successfully". - Hide the Moonlight pairing card on native-only hosts (HostInfo.gamestream) — it could never receive a PIN there. - Per-row pending on unpair/approve/deny; PIN input maxLength 16 (was 8). Displays / Library: - "Arrange displays" save refreshes the settings card (it rewrites the policy), without clobbering unsaved Custom edits (re-seed only when the draft still matches the server). - Live-display list wrapped in QueryState so errors don't read as "no displays". - "Forever" keep-alive option in the custom editor; edit-game form round-trips the logo artwork (was dropped on save); per-card delete pending. Stats: - Distinct colour for the native "queue" latency stage (it collided with "capture"). - "Not measured on this path" note on the GameStream health chart; configured-bitrate target line on throughput; host-authoritative elapsed timer; LiveCard surfaces non-404 errors. Shell / auth / i18n: - SSR-stable locale: first client render matches the base-locale SSR (no hydration mismatch), then adopts the persisted/browser locale post-hydration. - BFF proxy maps an upstream (mgmt-token) 401 to 502 so a logged-in user isn't bounced into a post-login redirect loop. - Logout checks the POST result before navigating; logs dedup by seq (StrictMode); login "next" keeps query/hash; Dashboard shows the active-session count. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
62 lines
2.0 KiB
TypeScript
62 lines
2.0 KiB
TypeScript
// The fetch mutator orval-generated hooks call: `apiFetch<T>(url, RequestInit)`. orval is
|
|
// configured (includeHttpResponseReturnType: false) so `T` is the response BODY; on an HTTP
|
|
// error we THROW an `ApiError` so React Query's `isError` works (the query client skips
|
|
// retries on 4xx — see src/router.tsx).
|
|
//
|
|
// Auth: requests are same-origin to `/api/...`; the browser sends only the session cookie
|
|
// (the server-side proxy injects the management bearer token — the token never lives in the
|
|
// browser). A 401 means the session is gone → bounce to /login.
|
|
|
|
/** A failed API call. `status` is the HTTP code; `data` is the parsed `ApiError` body if any. */
|
|
export class ApiError extends Error {
|
|
status: number;
|
|
data: unknown;
|
|
constructor(status: number, data: unknown, message?: string) {
|
|
super(message ?? `API error ${status}`);
|
|
this.name = "ApiError";
|
|
this.status = status;
|
|
this.data = data;
|
|
}
|
|
}
|
|
|
|
export async function apiFetch<T>(
|
|
url: string,
|
|
options?: RequestInit,
|
|
): Promise<T> {
|
|
const headers = new Headers(options?.headers);
|
|
headers.set("Accept", "application/json");
|
|
|
|
const res = await fetch(url, {
|
|
...options,
|
|
headers,
|
|
credentials: "same-origin",
|
|
});
|
|
|
|
const text = await res.text();
|
|
const body = text ? safeJson(text) : undefined;
|
|
if (res.status === 401) redirectToLogin();
|
|
if (!res.ok) throw new ApiError(res.status, body, res.statusText);
|
|
return body as T;
|
|
}
|
|
|
|
/** On lost session, send the user to the login screen, remembering where they were. */
|
|
function redirectToLogin(): void {
|
|
if (typeof window === "undefined") return;
|
|
if (window.location.pathname === "/login") return;
|
|
// Keep the full path (query + hash too), so re-login returns to the exact view.
|
|
const next = encodeURIComponent(
|
|
window.location.pathname + window.location.search + window.location.hash,
|
|
);
|
|
window.location.href = `/login?next=${next}`;
|
|
}
|
|
|
|
function safeJson(text: string): unknown {
|
|
try {
|
|
return JSON.parse(text);
|
|
} catch {
|
|
return text;
|
|
}
|
|
}
|
|
|
|
export default apiFetch;
|