Files
gerbeur/api/lib/pagination.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

53 lines
1.4 KiB
TypeScript

/**
* Pages every list route the same way. It reads the page a list route's query
* string asks for, and cuts the rows a service fetched into that page, which
* the routes send as `PaginatedData`.
*
* @module
*/
import { PAGINATION_DEFAULT_LIMIT, PAGINATION_MAX_LIMIT } from "../config.ts";
/**
* Reads the `page` and `limit` query parameters of a list route. It never
* fails: a missing or invalid `page` reads as 1, and `limit` is kept between 1
* and {@link PAGINATION_MAX_LIMIT}.
*/
export function parsePagination(
params: URLSearchParams,
defaultLimit = PAGINATION_DEFAULT_LIMIT,
): { page: number; limit: number } {
const page = Math.max(
1,
parseInt(params.get("page") ?? "1") || 1,
);
const limit = Math.min(
Math.max(
1,
parseInt(params.get("limit") ?? String(defaultLimit)) || defaultLimit,
),
PAGINATION_MAX_LIMIT,
);
return { page, limit };
}
/**
* Returned to the routes by the services' list functions, and sent as
* `PaginatedData`.
*/
export interface Page<T> {
items: T[];
hasMore: boolean;
}
/**
* Turns rows fetched with `LIMIT limit + 1` into a page. The extra row, when it
* comes back, is dropped and tells that another page follows, which spares a
* COUNT(*) over the whole list.
*/
export function pageOf<T>(rows: T[], limit: number): Page<T> {
return rows.length > limit
? { items: rows.slice(0, limit), hasMore: true }
: { items: rows, hasMore: false };
}