Files
gerbeur/shared/notification.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

156 lines
4.3 KiB
TypeScript

/**
* Notifications tell a user when someone follows them or their playlists,
* upvotes, comments, likes or mentions them, or posts where they follow. This
* module types the ones `api/services/notification-service.ts` makes, and the
* data each kind carries. The client's `/notifications` page lists them and
* turns each into a sentence and a link.
*
* @module
*/
/**
* Says which of the `…Data` interfaces a notification's `data` is. Each value
* has one `notify…` trigger in `notification-service.ts`.
*/
export type NotificationType =
| "playlist_followed"
| "user_followed"
| "user_dump_posted"
| "playlist_dump_added"
| "dump_upvoted"
| "user_mentioned"
| "dump_commented"
| "comment_liked";
/**
* Where a notification's dump is now, for its link (`dumpPath`). The server
* joins it each time it sends the notification, so a renamed dump or poster
* still links right; it is absent once the dump is deleted.
*/
export interface DumpRef {
dumpSlug?: string;
dumpOwnerUsername?: string;
}
/** Where a notification's playlist is now, joined as {@link DumpRef} is. */
export interface PlaylistRef {
playlistSlug?: string;
playlistOwnerUsername?: string;
}
/**
* Carried by a `playlist_followed` notification, sent to a playlist's owner.
*/
export interface PlaylistFollowedData extends PlaylistRef {
followerId: string;
followerUsername: string;
playlistId: string;
playlistTitle: string;
}
/** Carried by a `user_followed` notification, sent to the user followed. */
export interface UserFollowedData {
followerId: string;
followerUsername: string;
}
/**
* Carried by a `user_dump_posted` notification, sent to the followers of a
* user who posted a public dump.
*/
export interface UserDumpPostedData extends DumpRef {
dumperId: string;
dumperUsername: string;
dumpId: string;
dumpTitle: string;
}
/**
* Carried by a `playlist_dump_added` notification, sent to the followers of a
* public playlist when a public dump is added to it.
*/
export interface PlaylistDumpAddedData extends DumpRef, PlaylistRef {
dumpId: string;
dumpTitle: string;
playlistId: string;
playlistTitle: string;
}
/** Carried by a `dump_upvoted` notification, sent to the dump's poster. */
export interface DumpUpvotedData extends DumpRef {
voterId: string;
voterUsername: string;
dumpId: string;
dumpTitle: string;
}
/**
* Carried by a `user_mentioned` notification, sent to a user @mentioned in a
* comment, a dump, a playlist's description or a chat message. Its
* {@link DumpRef} is the dump's, or the comment's dump's; its
* {@link PlaylistRef} the playlist's.
*/
export interface UserMentionedData extends DumpRef, PlaylistRef {
mentionerId: string;
mentionerUsername: string;
contextType: "comment" | "dump" | "playlist" | "chat";
/** The id of the comment, dump, playlist or chat message. */
contextId: string;
/**
* The title of the dump or playlist, or of the dump a comment is under;
* empty for the chat.
*/
contextTitle: string;
/**
* Set only for a comment. It names the dump the comment is under, which the
* notification's link opens.
*/
dumpId?: string;
}
/** Carried by a `dump_commented` notification, sent to the dump's poster. */
export interface DumpCommentedData extends DumpRef {
commenterId: string;
commenterUsername: string;
commentId: string;
dumpId: string;
dumpTitle: string;
}
/** Carried by a `comment_liked` notification, sent to the comment's author. */
export interface CommentLikedData extends DumpRef {
likerId: string;
likerUsername: string;
commentId: string;
dumpId: string;
dumpTitle: string;
}
/**
* Stored when the notification is made, so a title changed later still shows
* the old one. The `…Username` fields and the refs are joined when it is sent,
* so they follow a rename. The notification's `type` says which member it is.
*/
export type NotificationData =
| PlaylistFollowedData
| UserFollowedData
| UserDumpPostedData
| PlaylistDumpAddedData
| DumpUpvotedData
| UserMentionedData
| DumpCommentedData
| CommentLikedData;
/**
* Pushed to its user's sockets in a `notification_created` message when it is
* made, and returned by `GET /api/me/notifications`.
*/
export interface Notification {
id: string;
userId: string;
type: NotificationType;
data: NotificationData;
read: boolean;
createdAt: Date;
}