Files
pn-new-crm/src/hooks/use-search.ts

58 lines
1.8 KiB
TypeScript
Raw Normal View History

'use client';
import { useQuery } from '@tanstack/react-query';
import { apiFetch } from '@/lib/api/client';
import { useDebounce } from '@/hooks/use-debounce';
// ─── Types ────────────────────────────────────────────────────────────────────
interface SearchResults {
refactor(clients): drop deprecated yacht/company/proxy columns PR 13: now that all reads are migrated to the dedicated yacht / company / membership entities, drop the columns that mirrored them on `clients`: companyName, isProxy, proxyType, actualOwnerName, relationshipNotes, yachtName, yachtLength{Ft,M}, yachtWidth{Ft,M}, yachtDraft{Ft,M}, berthSizeDesired. Migration `0008_loud_ikaris.sql` issues the destructive ALTER TABLE DROP COLUMN statements. Run `pnpm db:push` (or the migration runner) to apply. Caller cleanup (zero behavioral change to remaining flows): - Drops the legacy `generateEoi` flow entirely (route, service function, pdfme template, validator schema). The dual-path generate-and-sign service from PR 11 has fully replaced it; the route was no longer wired to the UI. - `clients.service`: company-name search column / WHERE / audit value removed; search now ranks by full name only. - `interests.service`: `resolveLeadCategory` reads dimensions from `yachts` via `interest.yachtId` instead of the dropped `client.yachtLength{Ft,M}`. - `record-export`: client-summary now lists yachts via owner-side lookup (direct + active company memberships); interest-summary fetches yacht via `interest.yachtId`. Both PDF templates updated to read yacht details from the new entity. - `client-detail-header`, `client-picker`, `command-search`, `search-result-item`, `use-search` hook, `types/domain.ts`, `search.service` — drop the companyName badge / sub-label / typed field everywhere it was rendered or fetched. - `ai.ts` worker: drop the company / yacht context lines from the prompt (will be re-added later sourced from the new entities). - `validators/interests.ts`: remove the deprecated public-form flat yacht/company fields. The route already ignores them. - `factories.ts`: drop the `isProxy: false` default. Tests: 652/652 green; type-check clean. The `security-sensitive-data` tests use `companyName` / `isProxy` as arbitrary record keys for a generic util — left unchanged. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-26 13:57:54 +02:00
clients: Array<{ id: string; fullName: string }>;
interests: Array<{
id: string;
clientName: string;
berthMooringNumber: string | null;
pipelineStage: string;
}>;
berths: Array<{ id: string; mooringNumber: string; area: string | null; status: string }>;
yachts: Array<{
id: string;
name: string;
hullNumber: string | null;
registration: string | null;
}>;
companies: Array<{
id: string;
name: string;
legalName: string | null;
taxId: string | null;
}>;
}
// ─── Hook ─────────────────────────────────────────────────────────────────────
export function useSearch(query: string) {
const debouncedQuery = useDebounce(query, 300);
const searchQuery = useQuery<SearchResults>({
queryKey: ['search', debouncedQuery],
queryFn: () =>
apiFetch<SearchResults>(`/api/v1/search?q=${encodeURIComponent(debouncedQuery)}`),
enabled: debouncedQuery.length >= 2,
staleTime: 30_000,
});
const recentQuery = useQuery<{ searches: string[] }>({
queryKey: ['search', 'recent'],
queryFn: () => apiFetch<{ searches: string[] }>('/api/v1/search/recent'),
staleTime: 60_000,
});
return {
results: searchQuery.data,
isLoading: searchQuery.isLoading,
recentSearches: recentQuery.data?.searches ?? [],
};
}