Files
Stirling-PDF/frontend/portal/src/api/http.ts
T
James BruntonandGitHub 3f7e898c69 Add sources service and frontend (#6774)
# Description of Changes
Redesign policies backend to treat sources a lot closer to how the
frontend imagined them working (they're persistent now and have an API).
Then connect the portal to the sources when mocks are off to allow for
source creation in the UI. It's not particularly useful to do that right
now because there's no policies UI, but I've tested manually that
sources set up in the UI are usable by policies created via the API.

I had to change the portal so that when mocks are off, it doesn't just
hard crash when attempting to connect to all the backend APIs that don't
exist yet. It'll still log the errors, but just continues on rendering
the UI now.

I also changed all the policies backend APIs to be gated behind a flag
instead of behind the SaaS profile. This is because we haven't yet got
the payment model sorted, but we're going to need this stuff running
self-hosted to be able to test it locally.
2026-06-26 13:21:53 +00:00

89 lines
2.7 KiB
TypeScript

/**
* Shared HTTP plumbing for the portal's service layer.
*
* Every `api/*.ts` module calls {@link httpJson}, which issues a real `fetch`.
* In dev and Storybook those requests are intercepted by the MSW handlers in
* `mocks/` and answered with fixture data; pointing at a real backend is just
* a matter of not registering MSW. Consumers don't change either way.
*
* The shared `stirling_jwt` bearer token (set by the auth gate, and shared
* same-origin with the editor) is attached automatically so portal data calls
* are authenticated once real backend endpoints exist.
*/
import { getStoredToken } from "@shared/auth";
export interface HttpRequestOptions {
method?: "GET" | "POST" | "PUT" | "PATCH" | "DELETE";
body?: unknown;
/** Extra headers; Content-Type and Accept are set automatically. */
headers?: Record<string, string>;
signal?: AbortSignal;
}
export class HttpError extends Error {
constructor(
public readonly status: number,
public readonly statusText: string,
public readonly body: unknown,
) {
super(`${status} ${statusText}`);
this.name = "HttpError";
}
}
/**
* Best-effort human-readable message from a thrown error: unwraps an
* {@link HttpError}'s ProblemDetail-ish body (`detail` / `message` / `error`)
* before falling back to the error's own message. Shared by views that surface
* a failed request inline.
*/
export function errorMessage(error: unknown): string {
if (error instanceof HttpError) {
const body = error.body as {
detail?: string;
message?: string;
error?: string;
} | null;
return body?.detail ?? body?.message ?? body?.error ?? error.message;
}
return error instanceof Error ? error.message : String(error);
}
function authHeader(): Record<string, string> {
const token = getStoredToken();
return token ? { Authorization: `Bearer ${token}` } : {};
}
/**
* Thin JSON fetch wrapper used by every api module. In dev/Storybook the
* request is served by MSW; against a real backend it hits the network.
*/
export async function httpJson<T>(
path: string,
options: HttpRequestOptions = {},
): Promise<T> {
const res = await fetch(path, {
method: options.method ?? "GET",
headers: {
Accept: "application/json",
...(options.body !== undefined
? { "Content-Type": "application/json" }
: {}),
...authHeader(),
...options.headers,
},
body: options.body !== undefined ? JSON.stringify(options.body) : undefined,
signal: options.signal,
});
if (!res.ok) {
let body: unknown = null;
try {
body = await res.json();
} catch {
// ignore — non-JSON error response
}
throw new HttpError(res.status, res.statusText, body);
}
return (await res.json()) as T;
}