d0540dca55
8 API route files were exporting handler functions directly from route.ts, which Next.js 15 rejects with "$NAME is not a valid Route export field". Per CLAUDE.md convention, service-tested handler functions live in sibling handlers.ts files and route.ts only re-exports the GET/POST/etc. wrapped in withAuth(withPermission(...)). Discovered during the mobile-foundation Task 24 build validation; the route files predate this branch but the build was never re-run on data-model. Files: - berth-reservations/[id], companies/autocomplete, companies/[id]/members + nested mid/set-primary, yachts/autocomplete, yachts/[id]/transfer, yachts/[id]/ownership-history - Integration tests updated to import from handlers.ts (companies, memberships, reservations, yachts-detail) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
19 lines
574 B
TypeScript
19 lines
574 B
TypeScript
import { NextResponse } from 'next/server';
|
|
|
|
import { type RouteHandler } from '@/lib/api/helpers';
|
|
import { errorResponse } from '@/lib/errors';
|
|
import { autocomplete } from '@/lib/services/companies.service';
|
|
|
|
export const autocompleteHandler: RouteHandler = async (req, ctx) => {
|
|
try {
|
|
const q = req.nextUrl.searchParams.get('q');
|
|
if (!q) {
|
|
return NextResponse.json({ data: [] });
|
|
}
|
|
const companies = await autocomplete(ctx.portId, q);
|
|
return NextResponse.json({ data: companies });
|
|
} catch (error) {
|
|
return errorResponse(error);
|
|
}
|
|
};
|