Expand useRealtimeRunsWithTag hook to support date range & run status filtering
Closes #1487
✅ Checklist
- [ ] I have followed every step in the contributing guide
- [ ] The PR title follows the convention.
- [ ] I ran and tested the code works
Testing
- Added
filtersoption withstatus,startDate, andendDate. - Verified that client-side filtering correctly narrows down results.
- Confirmed existing functionality without filters still works.
- Tested in Next.js client component with multiple tags.
Changelog
-
Extended
useRealtimeRunsWithTagto accept optionalfilters. -
Supported filters:
-
status: filter runs by one or multiple statuses. -
startDate&endDate: filter runs within a specific date range.
-
Pls check and tell if needed some changes
⚠️ No Changeset found
Latest commit: 1e8622cdb4580591594cda6d998ba914448d08d7
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
Walkthrough
Client-side filtering is introduced for realtime runs using a new RealtimeFilterOptions (startDate, endDate, statuses). The hook useRealtimeRunsWithTag now accepts filters via options and recomputes a filtersKey to restart streaming when filters change. Runs are post-filtered locally with useMemo. Server-side skipColumns-based filtering is removed from all subscriptions and processing paths. Ordering for inserted runs changes from createdAt to number. Exported/public API changes: added RealtimeFilterOptions, removed UseRealtimeRunsWithTagOptions, removed skipColumns from UseRealtimeSingleRunOptions, and updated the useRealtimeRunsWithTag signature accordingly. Additional utilities handle date/status extraction, normalization, and stable filter keys.
Estimated code review effort
🎯 3 (Moderate) | ⏱️ ~25 minutes
[!TIP]
🔌 Remote MCP (Model Context Protocol) integration is now available!
Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.
✨ Finishing Touches
- [ ] 📝 Generate Docstrings
🧪 Generate unit tests
- [ ] Create PR with unit tests
- [ ] Post copyable unit tests in a comment
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.
🪧 Tips
Chat
There are 3 ways to chat with CodeRabbit:
- Review comments: Directly reply to a review comment made by CodeRabbit. Example:
-
I pushed a fix in commit <commit_id>, please review it. -
Open a follow-up GitHub issue for this discussion.
-
- Files and specific lines of code (under the "Files changed" tab): Tag
@coderabbitaiin a new review comment at the desired location with your query. - PR comments: Tag
@coderabbitaiin a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:-
@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase. -
@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
-
Support
Need help? Create a ticket on our support page for assistance with any issues or questions.
CodeRabbit Commands (Invoked using PR/Issue comments)
Type @coderabbitai help to get the list of available commands.
Other keywords and placeholders
- Add
@coderabbitai ignoreanywhere in the PR description to prevent this PR from being reviewed. - Add
@coderabbitai summaryto generate the high-level summary at a specific location in the PR description. - Add
@coderabbitaianywhere in the PR title to generate the title automatically.
CodeRabbit Configuration File (.coderabbit.yaml)
- You can programmatically configure CodeRabbit by adding a
.coderabbit.yamlfile to the root of your repository. - Please see the configuration documentation for more information.
- If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation:
# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
Status, Documentation and Community
- Visit our Status Page to check the current availability of CodeRabbit.
- Visit our Documentation for detailed information on how to use CodeRabbit.
- Join our Discord Community to get help, request features, and share feedback.
- Follow us on X/Twitter for updates and announcements.