docs: plan for searching across previous company names#133
Conversation
Option-B feature plan: a materialized search_names table (current + former names) with a gin_trgm_ops index, so sponsors can be found by a former Companies House name (e.g. "Motodynamics Ltd" -> PhysicsX). Planning doc only — no code changes. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 33 minutes and 34 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
Summary
Feature plan for searching sponsors by their previous company names — e.g. typing
Motodynamics Ltd(ormotodynamics) surfaces PhysicsX, which Companies House records under that former name. Planning doc only — no code changes.Chooses Option B: a materialized
search_namestable (current and former names) with agin_trgm_opsindex, so former names get the same fuzzy/prefix matching as current names via a single trigram scan — replacing today's single-tablesearchHmrcquery.What the plan covers
search_namesschema + GIN trigram index (Drizzle)searchHmrcCTE rewrite (best-name-per-org → join back, small previous-match penalty)matchedFormerNameAPI/type addition +HmrcCard"Formerly …" hint (with pretext card-height note)Records why Option B was chosen over Option A (inline exact match). Independent of the
feat/previous-companiesPR — readscompanies_house_profiles.previous_company_namesdirectly — and branched offmain.📄
docs/search-previous-names-plan.md🤖 Generated with Claude Code