trails/apps/journal/app/routes/users.$username.following.tsx
Ullrich Schäfer df562742e1
fix(journal): extract loaders/actions for the remaining 21 mixed routes
Completes the .server.ts split started in #418. Every route that mixes
a default-export component with a server-only loader/action now has a
sibling <route>.server.ts holding the data-fetching helpers; the route
.tsx is a thin delegator.

Routes converted (21):
  activities._index, activities.$id, activities.new, auth.accept-terms,
  auth.verify, explore, feed, notifications, routes._index, routes.$id,
  routes.$id.edit, routes.new, settings, settings.account,
  settings.connections.komoot, settings.profile, settings.security,
  sync.import.$provider, sync.import.komoot, users.$username.followers,
  users.$username.following

Pattern (same as home.tsx / users.$username.tsx / settings.connections.tsx):
- loader → `return data(await loadX(request, params?))`
- action → `return await xAction(request, params?)`
- All `getDb` / Drizzle schema / `~/lib/*.server` imports move to the
  .server.ts sibling.
- `throw redirect(...)` and `throw data(...)` propagate through the
  delegator unchanged.

No behavior changes — pure module-graph cleanup. Component modules no
longer transitively import the DB client; Vite's tree-shake of
server-only code is now backed by an explicit, file-local contract.

Verified:
- pnpm typecheck — green
- pnpm lint — green
- pnpm test — 181 passed, 31 integration-gated skipped
- pnpm --filter @trails-cool/journal build — succeeds

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-24 11:05:40 +02:00

16 lines
650 B
TypeScript

import { data } from "react-router";
import type { Route } from "./+types/users.$username.following";
import { CollectionPage } from "~/components/CollectionPage";
import { loadUserFollowing } from "./users.$username.following.server";
export async function loader({ params, request }: Route.LoaderArgs) {
return data(await loadUserFollowing(request, params.username));
}
export function meta({ data: d }: Route.MetaArgs) {
return [{ title: `Following of @${d?.user.username ?? ""} — trails.cool` }];
}
export default function Following({ loaderData }: Route.ComponentProps) {
return <CollectionPage kind="following" {...loaderData} />;
}