Files
gerbeur/src/components/profile/ProfileInviteesTab.tsx
khannurien 07ac4bc629
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 paged list loads its pages one way, PlaylistDetail is split like the profile, and the comments keep the README's rules — Index, FollowedFeed, useUserDumpFeed, UserPlaylists, UserListPopover, Notifications, Search and the profile's followed users each hand-wrote "fetch the next page, append it, clear loadingMore on failure". A list the API pages is now a PagedList whose next page useLoadMore appends, and a list that loads on its own goes through usePagedList, which is useFetchState (now taking an initial value, as a restored cache, that starts loaded) plus useLoadMore. Pages are read by pageUrl with readPage (a refusal throws) or readFirstPage (a refusal is empty, as fetchFirstPage was), signed-in reads go through authFetch, and useFeedCache's saveState takes the list. Notifications keeps the socket's arrivals as their own list merged at render, as Index does with recentDumps, and marks them read in one effect. PlaylistDetail (963 lines) only puts the pieces together (146): usePlaylist holds the playlist, its live sync and its edits, PlaylistHeader, PlaylistEditForm and PlaylistDumpList are one file each, and LiveDumpCard is the vote wiring DumpCardList and the playlist both use. What it re-invented is shared: the load is useFetchState, a dump going private and back is usePositionAwareSync, deletes and edits are useDumpListSync (which also keeps comment counts, which the page didn't). A removal is sent when its fade ends, or as the page is left, so an undo sends nothing: the removal/re-add/reorder dance, the pending-undo order and the 80 ms debounce of its echoes are gone. A refused reorder goes back to the server's last order and says so, instead of reloading the page. The comments written since the documentation pass broke its rules in places: module docs as a label and a colon ("The "dumps" tab of a profile: …"), noun-phrase fragments on types, fields and constants, stale lists of callers, over-long lines; they are sentences now, and the ones the refactor made wrong (PlaylistDetail as useFading's and FollowPlaylistButton's caller, "the profiles" as usePositionAwareSync's only users) say what is true. 650 frontend and 214 backend tests pass (new: usePagedList, useFetchState's initial, pageUrl/readPage, the deferred removal, a dump returning at its place in a playlist), and tsc, eslint, doc:lint, deno check, deno lint and deno fmt are clean.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-29 21:19:33 +00:00

91 lines
2.6 KiB
TypeScript

/**
* Renders the "invitees" tab of a profile, which shows whom the user invited,
* and whom they invited in turn.
*
* @module
*/
import { useMemo } from "react";
import { Link } from "react-router";
import { Trans } from "@lingui/react/macro";
import type { Invitee } from "../../../shared/user.ts";
import type { FetchState } from "../../hooks/shared/useFetchState.ts";
import { Avatar } from "../shared/Avatar.tsx";
import { ListState } from "../shared/ListState.tsx";
import { ProfileSection } from "./ProfileSection.tsx";
type InviteTreeNode = Invitee & { children: InviteTreeNode[] };
/**
* Returns the invitees of `parentId` among `entries`, each with theirs. The
* server answers the whole tree as a flat list.
*/
function buildInviteTree(
entries: Invitee[],
parentId: string,
): InviteTreeNode[] {
return entries
.filter((e) => e.invitedById === parentId)
.map((e) => ({ ...e, children: buildInviteTree(entries, e.id) }));
}
/** Renders the invite tree, each invitee nested under who invited them. */
function InviteTreeList({ nodes }: { nodes: InviteTreeNode[] }) {
return (
<ul className="invite-tree">
{nodes.map((node) => (
<li key={node.id} className="invite-tree-node">
<Link
to={`/users/${node.username}`}
className="invite-tree-user"
>
<Avatar
userId={node.id}
username={node.username}
hasAvatar={!!node.avatarMime}
size={24}
/>
@{node.username}
</Link>
{node.children.length > 0 && <InviteTreeList nodes={node.children} />}
</li>
))}
</ul>
);
}
/** Passed to {@link ProfileInviteesTab} by `UserPublicProfile`. */
export interface ProfileInviteesTabProps {
userId: string;
/**
* Loaded when the tab is first opened, from
* `GET /api/users/:username/invitees`.
*/
state: FetchState<Invitee[]>;
}
/** Renders the invitees of `userId` as a tree. */
export function ProfileInviteesTab(
{ userId, state }: ProfileInviteesTabProps,
): React.JSX.Element {
const nodes = useMemo(
() => state.status === "loaded" ? buildInviteTree(state.data, userId) : [],
[state, userId],
);
return (
<ProfileSection title={<Trans>Invitees</Trans>}>
<ListState
state={state}
isEmpty={({ data }) => data.length === 0}
empty={
<p className="empty-state invite-tree-empty">
<Trans>No invitees yet.</Trans>
</p>
}
>
{() => <InviteTreeList nodes={nodes} />}
</ListState>
</ProfileSection>
);
}