admin/linkder
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

M2: the full job lifecycle — chat, hiring, geocoding, quotes, bookings, reviews

Browse Source 
Closes the funnel. Before this the product could match two people and then
stopped: `quotes`, `bookings` and `reviews` had tables and state machines and
nothing that wrote a row, the entry deck's right swipe was wired to an empty
handler, and every address resolved to the city centre.

Jobs tab and chat
- message router: thread, send, markRead, unreadTotal. A thread is a MATCH, not
  a job — one job with three interested pros is three private conversations.
- Current/Past segments derived from ACTIVE_JOB_STATUSES, job detail listing the
  pros who accepted, and the conversation itself with attachments.

Hiring from the deck
- A right swipe on the entry deck opened nothing. It now resolves "which job?"
  through a sheet — sign in, pick an open job, or post one — and calls the same
  deck.swipe the per-job deck does, so the open-request cap and row lock apply
  exactly once. Swipes are vetoable so closing the sheet returns the card.

Geocoding
- ST_Distance and ST_DWithin rank and filter every deck, and both operands were
  placeholders. Addresses now resolve through Mapbox (permanent=true, which is
  what licenses storing the coordinates), the server resolves points rather than
  trusting client-supplied lat/lng, and every stored point records how it was
  obtained. A `city`-precision base cannot reach the verification queue.

Quote -> booking -> review
- The commercial chain, minus payments. Accepting a quote is the only place a
  booking is created; confirming completion is what unlocks reviews and moves
  the pro's completed_jobs.
- Reviews publish double-blind with no sweeper: each is written with
  published_at already set to its embargo deadline and every read filters
  published_at <= now(), so it publishes itself. The second review pulls both
  forward. A silent counterparty cannot bury a bad review by never replying.

State machine changes, both deliberate
- booked -> matched: a cancelled booking is not a cancelled job.
- scheduled -> awaiting_confirmation: in_progress is optional, so a pro who
  never tapped Start can still say the work is done.

Test suite
- api tests ran files in parallel against one database and failed roughly one
  run in three on whichever file lost the race. Serialised, and three fixtures
  that grabbed "the first client" pinned to the seeded accounts.

Also includes work from a parallel session: admin verification queue, pro
public profile and reviews read path, notification sending, denormalised stats
recompute, search, and observability.

318 tests passing; typecheck and lint clean across 7 packages.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
serfa
2026-08-21 06:29:59 -04:00
co-authored by Claude Opus 5
parent 8f3509d1dd
commit 974e312534
115 changed files with 19994 additions and 569 deletions
Download Patch File Download Diff File Expand all files Collapse all files
apps/web/src/components/jobs/job-row.tsx
+154
View File
@@ -0,0 +1,154 @@
'use client';
import { CalendarClock, ChevronRight, MessageSquare, Users } from 'lucide-react';
import type { JobStatus } from '@linkder/shared';
import { cn, formatRelativeTime, formatWhen } from '@/lib/utils';
export type Perspective = 'client' | 'pro';
/**
* The status of a job, as a word and a tint. §8 — never colour alone.
*
* Two maps, because the same status means different things to the two sides.
* `matched` is "somebody said yes" to a customer and "you said yes" to a pro;
* one shared wording would fit neither, and a pro reading "Pros interested"
* about their own accepted job would reasonably think it was somebody else's.
*/
const STATUS: Record<Perspective, Record<JobStatus, { label: string; className: string }>> = {
client: {
open: { label: 'Looking for pros', className: 'border-brand-200 bg-brand-100 text-ink-950' },
matched: { label: 'Pros interested', className: 'border-go-100 bg-go-50 text-go-700' },
booked: { label: 'Booked', className: 'border-go-100 bg-go-50 text-go-700' },
completed: { label: 'Done', className: 'border-hairline bg-inset text-muted' },
cancelled: { label: 'Cancelled', className: 'border-stop-100 bg-stop-50 text-stop-600' },
},
pro: {
open: { label: 'Still open', className: 'border-brand-200 bg-brand-100 text-ink-950' },
matched: { label: 'You accepted', className: 'border-go-100 bg-go-50 text-go-700' },
booked: { label: 'Booked', className: 'border-go-100 bg-go-50 text-go-700' },
completed: { label: 'Done', className: 'border-hairline bg-inset text-muted' },
cancelled: { label: 'Cancelled', className: 'border-stop-100 bg-stop-50 text-stop-600' },
},
};
export interface JobRowData {
id: string;
title: string;
status: JobStatus;
/** The second line. The trade for a client, the customer's name for a pro. */
subtitle: string;
createdAt: Date;
matchCount?: number;
pendingCount?: number;
unreadCount: number;
lastMessageAt: Date | null;
nextBookingAt: Date | null;
}
/**
* One line of live detail per row, chosen by priority rather than stacked.
*
* A row that shows unread messages AND a booking AND three pending requests is a
* row nobody reads. The order is what the person has to act on soonest: someone
* is waiting for a reply, then something is about to happen, then someone is
* waiting for a decision.
*/
function liveDetail(job: JobRowData): { icon: typeof Users; text: string; urgent: boolean } | null {
if (job.unreadCount > 0) {
return {
icon: MessageSquare,
text: job.unreadCount === 1 ? '1 new message' : `${job.unreadCount} new messages`,
urgent: true,
};
}
if (job.nextBookingAt) {
return { icon: CalendarClock, text: formatWhen(job.nextBookingAt), urgent: false };
}
if (job.matchCount) {
return {
icon: Users,
text: job.matchCount === 1 ? '1 pro accepted' : `${job.matchCount} pros accepted`,
urgent: false,
};
}
if (job.pendingCount) {
return {
icon: Users,
text: job.pendingCount === 1 ? '1 pro deciding' : `${job.pendingCount} pros deciding`,
urgent: false,
};
}
return null;
}
/**
* DESIGN.md §6.10, applied to a job rather than a pro.
*
* No thumbnail: a job's photos are of a broken boiler, and a 56px crop of one
* says nothing at a glance. The trade and the status carry the row instead.
*/
export function JobRow({
job,
perspective,
onOpen,
}: {
job: JobRowData;
perspective: Perspective;
onOpen: (jobId: string) => void;
}) {
const status = STATUS[perspective][job.status];
const detail = liveDetail(job);
const timestamp = job.lastMessageAt ?? job.createdAt;
return (
<button
type="button"
onClick={() => onOpen(job.id)}
className={cn(
'flex w-full items-center gap-3 rounded-card border border-hairline bg-raised p-4 text-left',
'transition-[border-color] duration-[120ms] ease-standard',
'hover:border-brand-500 active:border-brand-500',
)}
>
<span className="min-w-0 flex-1">
<span className="flex items-baseline justify-between gap-2">
<span className="truncate font-display text-h4 text-strong">{job.title}</span>
<span className="shrink-0 text-meta text-faint tabular-nums">
{formatRelativeTime(timestamp)}
</span>
</span>
<span className="mt-2 flex flex-wrap items-center gap-2">
<span
className={cn(
'inline-flex items-center rounded-pill border px-3 py-1 text-meta',
status.className,
)}
>
{status.label}
</span>
<span className="truncate text-body-sm text-muted">{job.subtitle}</span>
</span>
{detail && (
<span
className={cn(
'mt-1.5 flex items-center gap-1.5 text-meta',
detail.urgent ? 'font-semibold text-accent' : 'text-faint',
)}
>
<detail.icon className="h-3.5 w-3.5 shrink-0" aria-hidden />
{detail.text}
</span>
)}
</span>
<ChevronRight className="h-4 w-4 shrink-0 text-accent" aria-hidden />
</button>
);
}
/** Placeholder at the row's own height, so the list does not jump when it lands. */
export function JobRowSkeleton() {
return <div className="h-[6.5rem] animate-pulse rounded-card bg-inset" aria-hidden />;
}