Files
gerbeur/shared/api.ts
khannurien f3f07ed1e3
All checks were successful
Build and Publish Docker Image / build-and-push (push) Successful in 49s
Build and Deploy Static Documentation Site / build-and-push (push) Successful in 22s
v3: every doc opens with the role, then the mechanism, then the details — the docs were written bottom-up: what a thing does first ("Declares the three contexts WSProvider fills…"), details that only make sense once its purpose is known next, and the reason it exists last ("…so that a feed doesn't re-render"), so a reader had nothing to hang the first sentences on. The README's rule caused it, since a module doc "opened with what the module does"; it now opens with the module's role in the app, and the value-side phrasing of a type ("Returned to Y by X") comes once the role is said, with WSContext as the before and after. WSContext.ts is rewritten that way throughout, and so are the docs elsewhere that buried their purpose in a trailing "so that" (the migrations, og, image-proxy, public-address, useFading, useFeedCache, the drafts), opened on a generic verb that hid it ("Holds", "Declares", "Loads", "Defines", "Types": the contexts and providers, the shared types, the models, the hooks), or were label fragments ("The page of a dump…", "A row of tabs."). A function whose verb is its action ("Stores session"), a props or result type, and a protocol message ("Sent by X when Y") already say their role and are left as they are. Only comments changed, and the catalogs only move their references; deno fmt, deno lint and doc:lint are clean.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-29 21:42:08 +00:00

80 lines
2.3 KiB
TypeScript

/**
* Lets the client tell success from failure the same way for every JSON
* endpoint, through the envelope they all answer with. It also defines {@link
* Wire}, the form a type takes once it has crossed JSON. The routes build the
* envelope, and the frontend's API helpers unwrap it.
*
* @module
*/
/**
* Lists the codes an {@link APIError} carries, one per HTTP status. The
* backend's `APIException` derives its code from the status it is given, and
* the frontend shows the message without reading the code.
*/
export const APIErrorCode = {
BAD_REQUEST: "BAD_REQUEST",
UNAUTHORIZED: "UNAUTHORIZED",
FORBIDDEN: "FORBIDDEN",
/** Also answers for what exists but the caller may not see. */
NOT_FOUND: "NOT_FOUND",
CONFLICT: "CONFLICT",
RATE_LIMITED: "RATE_LIMITED",
SERVER_ERROR: "SERVER_ERROR",
/** Answers when another site, such as Bandcamp or YouTube, failed us. */
BAD_GATEWAY: "BAD_GATEWAY",
} as const;
/** Carried by the backend's `APIException`, and sent in an {@link APIError}. */
export type APIErrorCode = typeof APIErrorCode[keyof typeof APIErrorCode];
/**
* Sent in an {@link APIFailure}. The frontend shows `message` to the user, so
* it is written for them.
*/
export interface APIError {
code: APIErrorCode;
message: string;
}
/** Sent by a route that succeeded, around its payload. */
export interface APISuccess<T> {
success: true;
data: T;
error?: never;
}
/**
* Sent by the error middleware when a request fails, and by the few routes
* that answer an error themselves.
*/
export interface APIFailure {
success: false;
data?: never;
error: APIError;
}
/**
* Returned by every JSON endpoint. A reader tells the two apart by `success`.
*/
export type APIResponse<T> = APISuccess<T> | APIFailure;
/**
* Returned by the list endpoints, as the `data` of an {@link APISuccess}.
*/
export interface PaginatedData<T> {
items: T[];
hasMore: boolean;
/** The size of the whole list, set only by search, which shows it. */
total?: number;
}
/**
* `T` as the client reads it from JSON, over HTTP, the socket or
* localStorage, where every `Date` has become an ISO string.
*/
export type Wire<T> = T extends Date ? string
: T extends readonly (infer U)[] ? Wire<U>[]
: T extends object ? { [K in keyof T]: Wire<T[K]> }
: T;