docs: drop custom Search override#32
Conversation
The override existed only to curate Cmd+K empty-state links before 1.1.0. Native search.popular + CURATED_POPULAR (still shared with 404) replace it.
|
|
Warning Review limit reached
Next review available in: 11 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
✨ 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 |
Summary
apps/docs/components/blume/Search.astroand stop overriding layout Search.CURATED_POPULARas the source for Blumesearch.popularand the 404 page.Why
Custom Search was added in
ba10229only because Blume 1.0.4 had no curated empty-state API. Blume 1.1.0 shipssearch.popular; the fork was ignoring that config.Test plan
bun run docs:check -- --isolatedbun run docs:build