feat(search): message search for conversations and web console#22
Conversation
- Add ConversationService.searchMessagesInConversation for per-topic LIKE search with ESCAPE for % and _ wildcards - Add ConversationService.searchMessages for global cross-conversation search with pagination, JOIN to contacts and telegram_topics - Add /search <keyword> command in Topic, returns up to 20 matches - Add /operations/search web page with search box and paginated results table showing conversation, topic, contact, direction, text - Navigation header adds 搜索 tab - 3 new test cases: per-conversation search, global search with pagination, web search page rendering Co-authored-by: monkeycode-ai <monkeycode-ai@chaitin.com>
|
Warning Review limit reached
Next review available in: 49 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: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (5)
✨ 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
ConversationService.searchMessagesInConversation— per-topic LIKE search with ESCAPE for%and_wildcardsConversationService.searchMessages— global cross-conversation search with pagination, JOIN to contacts and telegram_topics/search <keyword>command in Topic — returns up to 20 matches with message previews/operations/searchweb page — search box + paginated results table (conversation, topic, contact, direction, text preview)Problem
/historyonly showed the last 30 messages. There was no way to find a specific message by keyword across conversation history or globally. Ops had to SQL query the database to find past messages.Verification
npm run verifypassed (check + 48 tests + audit 0 vulns)