feat(interests): linked berths list with role-flag toggles + EOI bypass
Implements plan §5.5: a per-interest "Linked berths" panel mounted above the
recommender on the interest detail Overview tab. Each junction row exposes
the role-flag controls reps need to manage the M:M `interest_berths` link
without the legacy single-berth flow.
UI (`src/components/interests/linked-berths-list.tsx`)
* Rows ordered with primary first; mooring number links to /berths/[id], with
area + a status pill (available/under_offer/sold) and a "Primary" chip.
* "Specifically pitching" Switch (writes `is_specific_interest`) with the
consequence text from §1: "This berth will appear as under interest on the
public map" / "This berth is hidden from the public map".
* "Mark in EOI bundle" Switch (writes `is_in_eoi_bundle`).
* "Set as primary" button when the row isn't primary - the existing
`upsertInterestBerth` helper demotes the prior primary in the same tx.
* "Bypass EOI for this berth" with reason textarea, ONLY rendered when the
parent interest's `eoiStatus === 'signed'`. Writes the bypass triple
(`eoi_bypass_reason`, `eoi_bypassed_by` = caller, `eoi_bypassed_at` = now);
also supports clearing.
* Remove-from-interest action gated by a confirmation dialog.
API (`src/app/api/v1/interests/[id]/berths/...`)
* `GET /` - list endpoint returning `listBerthsForInterest` plus the parent
interest's `eoiStatus` in `meta.eoiStatus` so the UI can decide whether to
show the bypass control.
* `PATCH /[berthId]` - partial update of the junction row's flags + bypass
fields. Server-side guard: rejects bypass writes when `eoiStatus !==
'signed'` (defence in depth - never trust the UI to gate this).
* `DELETE /[berthId]` - calls `removeInterestBerth`.
* The existing POST stays unchanged. All routes wrapped with
`withAuth(withPermission('interests', view|edit, ...))`. portId from ctx;
cross-port reads/writes return 404 for enumeration prevention (§14.10).
Service changes (`src/lib/services/interest-berths.service.ts`)
* `upsertInterestBerth` now accepts `eoiBypassReason` (tri-state: omit = no
change, non-empty = record, null = clear) and `eoiBypassedBy`. The bypass
triple moves as a unit, with `eoi_bypassed_at` stamped server-side.
* `listBerthsForInterest` now returns berth detail (area, status, dimensions)
alongside the junction row, typed as `InterestBerthWithDetails`.
Socket: added `interest:berthLinkUpdated` event for live UI refreshes.
Tests: 18 new integration tests in `tests/integration/api/interest-berths.test.ts`
covering happy paths, primary-demotion in same tx, bypass write/clear, the
"requires signed EOI" guard, cross-port 404s, missing-link 404s, empty-body
400, and viewer 403 through the permission gate.
2026-05-05 04:01:56 +02:00
|
|
|
import { NextResponse } from 'next/server';
|
|
|
|
|
import { and, eq } from 'drizzle-orm';
|
|
|
|
|
import { z } from 'zod';
|
|
|
|
|
|
|
|
|
|
import { type RouteHandler } from '@/lib/api/helpers';
|
|
|
|
|
import { parseBody } from '@/lib/api/route-helpers';
|
|
|
|
|
import { errorResponse, NotFoundError, ValidationError } from '@/lib/errors';
|
|
|
|
|
import { db } from '@/lib/db';
|
|
|
|
|
import { interests } from '@/lib/db/schema/interests';
|
|
|
|
|
import { berths } from '@/lib/db/schema/berths';
|
|
|
|
|
import { listBerthsForInterest, upsertInterestBerth } from '@/lib/services/interest-berths.service';
|
|
|
|
|
import { createAuditLog } from '@/lib/audit';
|
|
|
|
|
import { emitToRoom } from '@/lib/socket/server';
|
|
|
|
|
|
|
|
|
|
// ─── Schemas ────────────────────────────────────────────────────────────────
|
|
|
|
|
|
|
|
|
|
const addBerthSchema = z.object({
|
|
|
|
|
berthId: z.string().min(1),
|
|
|
|
|
/** Drives the public-map "Under Offer" sub-status. See plan §5.4. */
|
|
|
|
|
isSpecificInterest: z.boolean(),
|
|
|
|
|
});
|
|
|
|
|
|
|
|
|
|
// ─── GET /api/v1/interests/[id]/berths ──────────────────────────────────────
|
|
|
|
|
//
|
|
|
|
|
// Returns the linked-berths list (plan §5.5) along with the parent interest's
|
|
|
|
|
// `eoiStatus` so the UI can decide whether to show the EOI-bypass control.
|
|
|
|
|
// Tenant-scoped: 404 when the interest doesn't belong to the caller's port,
|
|
|
|
|
// matching the recommender route's enumeration-prevention behaviour.
|
|
|
|
|
export const listHandler: RouteHandler = async (_req, ctx, params) => {
|
|
|
|
|
try {
|
|
|
|
|
const interestId = params.id!;
|
|
|
|
|
const interest = await db.query.interests.findFirst({
|
|
|
|
|
where: eq(interests.id, interestId),
|
|
|
|
|
});
|
|
|
|
|
if (!interest || interest.portId !== ctx.portId) {
|
|
|
|
|
throw new NotFoundError('Interest');
|
|
|
|
|
}
|
|
|
|
|
const links = await listBerthsForInterest(interestId);
|
|
|
|
|
return NextResponse.json({
|
|
|
|
|
data: links,
|
|
|
|
|
meta: { eoiStatus: interest.eoiStatus },
|
|
|
|
|
});
|
|
|
|
|
} catch (error) {
|
|
|
|
|
return errorResponse(error);
|
|
|
|
|
}
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
// ─── POST /api/v1/interests/[id]/berths ─────────────────────────────────────
|
|
|
|
|
//
|
|
|
|
|
// Add a (non-primary) berth link to the interest. Defaults to
|
|
|
|
|
// `isInEoiBundle=false`, `isPrimary=false`; the rep can flip these later via
|
|
|
|
|
// the linked-berths list (PATCH route below).
|
|
|
|
|
export const addHandler: RouteHandler = async (req, ctx, params) => {
|
|
|
|
|
try {
|
|
|
|
|
const body = await parseBody(req, addBerthSchema);
|
|
|
|
|
const interestId = params.id!;
|
|
|
|
|
|
|
|
|
|
const interest = await db.query.interests.findFirst({
|
|
|
|
|
where: eq(interests.id, interestId),
|
|
|
|
|
});
|
|
|
|
|
if (!interest || interest.portId !== ctx.portId) {
|
|
|
|
|
throw new NotFoundError('Interest');
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
// Tenant scope: berth must belong to this port (never trust a client-
|
|
|
|
|
// supplied id to cross port boundaries — plan §14.10).
|
|
|
|
|
const berth = await db.query.berths.findFirst({
|
|
|
|
|
where: and(eq(berths.id, body.berthId), eq(berths.portId, ctx.portId)),
|
|
|
|
|
});
|
|
|
|
|
if (!berth) {
|
|
|
|
|
throw new ValidationError('berthId not found in this port');
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
const link = await upsertInterestBerth(interestId, body.berthId, {
|
|
|
|
|
isSpecificInterest: body.isSpecificInterest,
|
|
|
|
|
addedBy: ctx.userId,
|
|
|
|
|
});
|
|
|
|
|
|
|
|
|
|
void createAuditLog({
|
|
|
|
|
userId: ctx.userId,
|
|
|
|
|
portId: ctx.portId,
|
|
|
|
|
action: 'update',
|
|
|
|
|
entityType: 'interest',
|
|
|
|
|
entityId: interestId,
|
|
|
|
|
newValue: { berthId: body.berthId, isSpecificInterest: body.isSpecificInterest },
|
|
|
|
|
metadata: { type: 'berth_added_to_interest' },
|
|
|
|
|
ipAddress: ctx.ipAddress,
|
|
|
|
|
userAgent: ctx.userAgent,
|
|
|
|
|
});
|
|
|
|
|
|
|
|
|
|
emitToRoom(`port:${ctx.portId}`, 'interest:berthLinked', {
|
|
|
|
|
interestId,
|
|
|
|
|
berthId: body.berthId,
|
|
|
|
|
});
|
2026-05-05 04:20:38 +02:00
|
|
|
// Outbound webhook: the legacy /link-berth path dispatched
|
|
|
|
|
// `interest.berth_linked` and external integrations subscribe to it.
|
|
|
|
|
// The new junction-add path must keep that contract.
|
|
|
|
|
void import('@/lib/services/webhook-dispatch').then(({ dispatchWebhookEvent }) =>
|
|
|
|
|
dispatchWebhookEvent(ctx.portId, 'interest:berthLinked', {
|
|
|
|
|
interestId,
|
|
|
|
|
berthId: body.berthId,
|
|
|
|
|
}),
|
|
|
|
|
);
|
feat(interests): linked berths list with role-flag toggles + EOI bypass
Implements plan §5.5: a per-interest "Linked berths" panel mounted above the
recommender on the interest detail Overview tab. Each junction row exposes
the role-flag controls reps need to manage the M:M `interest_berths` link
without the legacy single-berth flow.
UI (`src/components/interests/linked-berths-list.tsx`)
* Rows ordered with primary first; mooring number links to /berths/[id], with
area + a status pill (available/under_offer/sold) and a "Primary" chip.
* "Specifically pitching" Switch (writes `is_specific_interest`) with the
consequence text from §1: "This berth will appear as under interest on the
public map" / "This berth is hidden from the public map".
* "Mark in EOI bundle" Switch (writes `is_in_eoi_bundle`).
* "Set as primary" button when the row isn't primary - the existing
`upsertInterestBerth` helper demotes the prior primary in the same tx.
* "Bypass EOI for this berth" with reason textarea, ONLY rendered when the
parent interest's `eoiStatus === 'signed'`. Writes the bypass triple
(`eoi_bypass_reason`, `eoi_bypassed_by` = caller, `eoi_bypassed_at` = now);
also supports clearing.
* Remove-from-interest action gated by a confirmation dialog.
API (`src/app/api/v1/interests/[id]/berths/...`)
* `GET /` - list endpoint returning `listBerthsForInterest` plus the parent
interest's `eoiStatus` in `meta.eoiStatus` so the UI can decide whether to
show the bypass control.
* `PATCH /[berthId]` - partial update of the junction row's flags + bypass
fields. Server-side guard: rejects bypass writes when `eoiStatus !==
'signed'` (defence in depth - never trust the UI to gate this).
* `DELETE /[berthId]` - calls `removeInterestBerth`.
* The existing POST stays unchanged. All routes wrapped with
`withAuth(withPermission('interests', view|edit, ...))`. portId from ctx;
cross-port reads/writes return 404 for enumeration prevention (§14.10).
Service changes (`src/lib/services/interest-berths.service.ts`)
* `upsertInterestBerth` now accepts `eoiBypassReason` (tri-state: omit = no
change, non-empty = record, null = clear) and `eoiBypassedBy`. The bypass
triple moves as a unit, with `eoi_bypassed_at` stamped server-side.
* `listBerthsForInterest` now returns berth detail (area, status, dimensions)
alongside the junction row, typed as `InterestBerthWithDetails`.
Socket: added `interest:berthLinkUpdated` event for live UI refreshes.
Tests: 18 new integration tests in `tests/integration/api/interest-berths.test.ts`
covering happy paths, primary-demotion in same tx, bypass write/clear, the
"requires signed EOI" guard, cross-port 404s, missing-link 404s, empty-body
400, and viewer 403 through the permission gate.
2026-05-05 04:01:56 +02:00
|
|
|
|
|
|
|
|
return NextResponse.json({ data: link }, { status: 201 });
|
|
|
|
|
} catch (error) {
|
|
|
|
|
return errorResponse(error);
|
|
|
|
|
}
|
|
|
|
|
};
|