feat(interests): EOI/contract/reservation tabs + contact log + berth interest milestone + interest list overhaul
Major interest workflow expansion driven by the rapid-fire UX session.
EOI / Contract / Reservation tabs replace the generic Documents tab when
the deal is at the relevant stage — workspace pattern with active-doc
hero, signing progress, paper-signed upload, and history strip. Stage-
conditional visibility wired through interest-tabs.tsx so the tab set
shrinks/expands as the deal moves through the pipeline.
Contact log: per-interaction structured log (channel/direction/summary/
optional follow-up reminder). New `interest_contact_log` table + service
+ tab UI (timeline with channel-coded icons + compose dialog).
auto-creates a reminder when followUpAt is set.
Berth Interest milestone: first milestone in the OverviewTab's pipeline
strip, completes the moment any berth is linked via the junction. Drives
the "have we captured what they want?" sanity check for general_interest
leads before they move to EOI.
Stage-conditional milestones: past phases collapse into a one-liner
strip, current phase expands, future phases hide behind a "Show
upcoming" toggle. Inline stage picker now defers reason capture to an
override-confirm view (only required for illegal transitions, not the
default flow).
Notes blob → threaded: dropped `interests.notes` column entirely; the
threaded `interest_notes` table is the single source of truth. Latest-
note teaser on Overview links into the dedicated Notes tab. Polymorphic
notes service gains aggregated client view (unions client + interest +
yacht notes with source chips and group-by-source toggle).
Berth interest list overhaul:
- Configurable columns via ColumnPicker (18 toggleable, 5 default-on)
- Natural-sort SQL ORDER BY on mooring number (A1, A2, A10 not A10, A2)
- Per-letter row tinting via colored left-border accent + dot in cell
- Documents tab merged Files (single attachments section)
Topbar improvements:
- Always-visible back arrow on detail pages (path depth > 2)
- Breadcrumb-hint store + useBreadcrumbHint hook so detail pages can
push their entity hierarchy (Clients › Mary Smith › Interest › B17)
- Tighter spacing, softer separators, 160px crumb truncation
DataTable upgrades:
- Page-size selector with All option (validator cap raised to 1000)
- getRowClassName slot for per-row styling (used by berth tinting)
- Fixed Radix SelectItem crash on empty-string values via __any__
sentinel (was crashing every list page that opened a select filter)
Interest list:
- Configurable columns picker
- Stage cell clickable into detail
- TagPicker + SavedViewsDropdown sized h-8 to match adjacent buttons
- Save view moved into ColumnPicker menu; Views button hidden when
no views are saved
- Pipeline kanban board endpoint at /api/v1/interests/board with
minimal projection, 5000-row cap + truncated banner, filter
pass-through
Mobile chrome + sidebar collapse removed (always-expanded design choice).
User management lists super-admins (was inner-joined on user_port_roles
which excluded global super-admins).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
37
src/app/api/v1/interests/[id]/contact-log/route.ts
Normal file
37
src/app/api/v1/interests/[id]/contact-log/route.ts
Normal file
@@ -0,0 +1,37 @@
|
||||
import { NextResponse } from 'next/server';
|
||||
|
||||
import { withAuth, withPermission } from '@/lib/api/helpers';
|
||||
import { parseBody } from '@/lib/api/route-helpers';
|
||||
import { errorResponse } from '@/lib/errors';
|
||||
import { create, listForInterest } from '@/lib/services/interest-contact-log.service';
|
||||
import { createContactLogSchema } from '@/lib/validators/interest-contact-log';
|
||||
|
||||
export const GET = withAuth(
|
||||
withPermission('interests', 'view', async (_req, ctx, params) => {
|
||||
try {
|
||||
const entries = await listForInterest(params.id!, ctx.portId);
|
||||
return NextResponse.json({ data: entries });
|
||||
} catch (error) {
|
||||
return errorResponse(error);
|
||||
}
|
||||
}),
|
||||
);
|
||||
|
||||
export const POST = withAuth(
|
||||
withPermission('interests', 'edit', async (req, ctx, params) => {
|
||||
try {
|
||||
const body = await parseBody(req, createContactLogSchema);
|
||||
const entry = await create(ctx.userId, {
|
||||
interestId: params.id!,
|
||||
occurredAt: body.occurredAt,
|
||||
channel: body.channel,
|
||||
direction: body.direction,
|
||||
summary: body.summary,
|
||||
followUpAt: body.followUpAt ?? null,
|
||||
});
|
||||
return NextResponse.json({ data: entry }, { status: 201 });
|
||||
} catch (error) {
|
||||
return errorResponse(error);
|
||||
}
|
||||
}),
|
||||
);
|
||||
26
src/app/api/v1/interests/[id]/eoi-context/route.ts
Normal file
26
src/app/api/v1/interests/[id]/eoi-context/route.ts
Normal file
@@ -0,0 +1,26 @@
|
||||
import { NextResponse } from 'next/server';
|
||||
|
||||
import { withAuth, withPermission } from '@/lib/api/helpers';
|
||||
import { errorResponse } from '@/lib/errors';
|
||||
import { buildEoiContext } from '@/lib/services/eoi-context';
|
||||
|
||||
/**
|
||||
* Returns the resolved `EoiContext` — the actual data that would be
|
||||
* auto-filled into the EOI document — for the given interest. Drives
|
||||
* the EOI generate dialog's pre-flight preview so a sales rep can see
|
||||
* (and correct) every value before sending the document for signing.
|
||||
*
|
||||
* No mutation; pure read of denormalized data the EOI builder already
|
||||
* computes server-side. Returns 404 if the interest is missing or in
|
||||
* another port (the buildEoiContext function throws NotFoundError).
|
||||
*/
|
||||
export const GET = withAuth(
|
||||
withPermission('interests', 'view', async (_req, ctx, params) => {
|
||||
try {
|
||||
const context = await buildEoiContext(params.id!, ctx.portId);
|
||||
return NextResponse.json({ data: context });
|
||||
} catch (error) {
|
||||
return errorResponse(error);
|
||||
}
|
||||
}),
|
||||
);
|
||||
30
src/app/api/v1/interests/board/route.ts
Normal file
30
src/app/api/v1/interests/board/route.ts
Normal file
@@ -0,0 +1,30 @@
|
||||
import { NextResponse } from 'next/server';
|
||||
|
||||
import { withAuth, withPermission } from '@/lib/api/helpers';
|
||||
import { parseQuery } from '@/lib/api/route-helpers';
|
||||
import { errorResponse } from '@/lib/errors';
|
||||
import { listInterestsForBoard } from '@/lib/services/interests.service';
|
||||
import { boardFiltersSchema } from '@/lib/validators/interests';
|
||||
|
||||
/**
|
||||
* Board (kanban) endpoint — returns every active interest for the port
|
||||
* with a minimal projection (id, clientName, mooring, leadCategory,
|
||||
* stage, updatedAt). No pagination: the kanban renders the whole
|
||||
* pipeline at once. The service hard-caps at 5000 rows to keep payload
|
||||
* size bounded; if `truncated: true` the UI surfaces a banner.
|
||||
*
|
||||
* Filter params are a strict subset of the list endpoint — see
|
||||
* boardFiltersSchema. `pipelineStage` and `includeArchived` are
|
||||
* intentionally rejected at validation time.
|
||||
*/
|
||||
export const GET = withAuth(
|
||||
withPermission('interests', 'view', async (req, ctx) => {
|
||||
try {
|
||||
const filters = parseQuery(req, boardFiltersSchema);
|
||||
const result = await listInterestsForBoard(ctx.portId, filters);
|
||||
return NextResponse.json(result);
|
||||
} catch (error) {
|
||||
return errorResponse(error);
|
||||
}
|
||||
}),
|
||||
);
|
||||
Reference in New Issue
Block a user