Files
gerbeur/shared/user.ts
khannurien 4468438ba7 v4: every page and API URL follows one of two rules, written down in API.md — pages are a hierarchy where @name is a user and any other root word a category or an app page, tabs and views are plain segments and a default view is the bare path; API resources are /api/<plural>/<key>, a user's key being an id or @name, the caller's things under /api/me, media a sub-resource, lookups by another key a query filter. ~ is gone: the feed is /, /hot, /new, /journal, /follow and /music/hot, a profile /@bob with its overview and the tabs dumps, upvoted, playlists (her own only), follow (users, and /follow/playlists), invitees and manage (role and name, for user:manage), which replace the separate UserDumps, UserUpvoted and UserPlaylists pages; /settings holds the account (now with the username) and /manage the category manager, both linked from the user menu and one's profile. Dumps and playlists live under their owner, /@bob/dumps/<slug> and /@bob/playlists/<slug>, named by slug alone: migration 0021 re-slugs them to the bare slugify(title), unique per owner and kind (the oldest keeps it, clashes get -2), renames the categories whose slug v4 reserves (hot, follow, settings…), and rewrites this site's v3 links in dump notes, comments, chat, and playlist and profile descriptions. A slug changes only when edited, through the edit forms' new link field, which proposes slugify(title) as the title changes; a username changes from /settings or, for user:manage, from /@name/manage. Every slug or name left behind stays an alias of its item or user for good (dump_slug_aliases, playlist_slug_aliases, user_aliases), so old links redirect without chaining and nobody else can take one; slugs change 3 times a day per item, names once in 30 days, moderators exempt. An alias, or a name in another case, answers the item with its current path: the pages put it in their URL (useCanonicalPath, without fetching again), and the OG middleware answers a 301. shared/paths.ts builds and parses every page path, for the client's links, the emails' (digest-service lost its own builders and its id fallbacks, and links /follow and /settings) and the server's matchers (OG tags, self previews, backlinks, self-url); shared/slug.ts holds slugify and the format categories share. Dumps and playlists carry ownerUsername and a required slug, and notifications join their users' current names and their items' paths each time they are sent or read, so renames reach them and a deleted item's has no link. The API was renamed per the plan's table: POST /api/users and /api/sessions, /api/password-resets, /api/me (with settings, password, avatar, media-token, playlists?contains=, follow, feed?from=, notifications), /api/users/:key/{dumps,upvoted,playlists,follow/users,follow/playlists,invitees,avatar} and by path /api/users/:key/{dumps,playlists}/:slug, /api/dumps?url= and ?category=, /api/dumps/:id/{file,thumbnail,metadata}, /api/playlists/:id/cover, /api/remote/{preview,image,bandcamp,youtube} (one router), and /api/unsubscribe, the v3 POST /api/users/unsubscribe staying for the digests already sent. A stored default feed tab "followed" reads as "follow" once. dumps.slug and playlists.slug stay nullable, since SQLite can't add NOT NULL without rebuilding tables others reference; every writer sets them and unique (user_id, slug) indexes hold them. 254 backend tests (new: migration 0021 on a v3 fixture, slug aliases, swaps and rate limits, username renames, aliases and limits, reads by path and their privacy, the OG 301s, both unsubscribe paths, v4-shaped digest links with no ids, notification joins, shared paths and slugs) and 668 frontend tests (new: the profile's tabs and follow views, Settings, Manage, the link field, canonical URLs on the dump, playlist and profile pages, bare default feed paths) pass, and tsc, eslint, deno check, deno lint, deno fmt and doc:lint are clean; the migration was also run on a copy of the development database.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-06 16:08:59 +00:00

150 lines
4.1 KiB
TypeScript

/**
* A user crosses the wire in several shapes: as anyone sees them, as they see
* themselves, and in the bodies and answers of the `/api/users` and
* `/api/invites` endpoints. This module types them all, with the roles, for the
* server and the client alike.
*
* @module
*/
/**
* Sets what a user may do beyond the basics, through `ROLE_PERMISSIONS`
* (`shared/permissions.ts`). An admin changes it with
* `PATCH /api/users/:key/role`.
*/
export type Role = "user" | "moderator" | "admin";
/** Every {@link Role}, least to most privileged. */
export const ROLES: readonly Role[] = ["user", "moderator", "admin"];
/**
* Checks whether `value` is a {@link Role}, as the role endpoint and the row
* guards must before trusting one.
*/
export function isRole(value: unknown): value is Role {
return typeof value === "string" &&
(ROLES as readonly string[]).includes(value);
}
/**
* Returned by every endpoint that shows a user to others: profiles, the users
* one follows, search results, and the `user_updated` socket message. The
* server makes it with `toPublicUser`, which drops the email.
*/
export interface PublicUser {
id: string;
/**
* Picked at sign-up, and changeable since, a former name staying an alias
* of the user for good. Pages write it as `@name` (`userPath`).
*/
username: string;
role: Role;
createdAt: Date;
/**
* Bumped by any profile or avatar change. The client uses it to reload the
* avatar.
*/
updatedAt?: Date;
/** Undefined without an avatar. */
avatarMime?: string;
/** Markdown. */
description?: string;
invitedByUsername?: string;
}
/**
* Returned to a user about themselves: by sign-up and sign-in in
* {@link AuthResponse}, by `GET /api/me`, and by an avatar upload.
*/
export interface SelfUser extends PublicUser {
/** Where password reset links go. It belongs to this account only. */
email: string;
}
/**
* Returned by `GET /api/users?q=` to the editor's @mention autocomplete.
*/
export interface UserSuggestion {
id: string;
username: string;
/** Null without an avatar. */
avatarMime: string | null;
}
/**
* Returned, as a flat list in sign-up order, by
* `GET /api/users/:key/invitees`. The profile page nests it into a tree
* by `invitedById`.
*/
export interface Invitee {
id: string;
username: string;
/** Undefined without an avatar. */
avatarMime?: string;
invitedById: string;
createdAt: Date;
}
/** Sent to `POST /api/sessions` by the login page. */
export interface LoginUserRequest {
username: string;
password: string;
}
/** Sent to `POST /api/users` by the register page. */
export interface RegisterUserRequest {
username: string;
password: string;
/** From the invite link the register page was opened with. */
inviteToken: string;
email: string;
}
/**
* Passed to `updateUser` by the users routes and the password reset, and sent
* by a client to `PATCH /api/me`, which takes only `description`, `email` and
* `username`; the role and the password change through their own endpoints,
* and the username through `renameUser`.
*/
export interface UpdateUserRequest {
username?: string;
password?: string;
role?: Role;
/** An empty string clears it. Null, like undefined, keeps it. */
description?: string | null;
email?: string;
}
/**
* Returned by sign-up, sign-in and a password change. The client keeps both
* tokens with its session.
*/
export interface AuthTokens {
/** Sent as `Authorization: Bearer …`, and as `?token=` to the WebSocket. */
token: string;
/**
* Carried as `?token=` by the URLs of private media. It can read media and
* nothing else.
*/
mediaToken: string;
}
/** Returned by sign-up and sign-in. */
export interface AuthResponse extends AuthTokens {
user: SelfUser;
}
/**
* Returned by `GET /api/me/media-token` to a session from before media
* tokens, which has none.
*/
export type MediaTokenResponse = Pick<AuthTokens, "mediaToken">;
/**
* Returned by `POST /api/invites` to the profile page, which builds the invite
* link from `token`.
*/
export interface InviteResponse {
token: string;
}