Feature/events pagination filtering#621
Conversation
- Add ?pageSize, ?streamId, and ?since query parameters - Updated getGlobalEvents and countAllEvents to support all filters - Updated listEventsQuerySchema with new optional fields - Changed default pagination to use pageSize=20 instead of returning all - Added Swagger documentation for the endpoint - Added integration tests covering each filter independently and combined Closes ritik4ever#380
…nts schema - Add 'completed' to VALID_EVENT_TYPES in schemas.ts and the swagger eventType enum to match the handler's accepted StreamEventType values - Add 400 error response to /api/events swagger definition - Reject blank streamId values (e.g. streamId=) at the schema boundary while keeping the field optional when omitted entirely
- streamStore.updateStartAt.test.ts: await async updateStreamStartAt calls - streamStore.progress.test.ts: cap elapsedSeconds at duration, handle zero duration - eventHistory.test.ts: pass asc order explicitly to getStreamHistory calls - streamStore.test.ts, streamStore.reconcile.test.ts: mock logger module - cors.test.ts: remove duplicate app.use(cors()) causing origin override - requestLogger.test.ts: mock setHeader in first test case - Add syncFtsIndex to dbMocks in 3 test files
|
Someone is attempting to deploy a commit to the ritik4ever's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
Warning Review limit reached
More reviews will be available in 23 minutes and 53 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more credits in the billing tab to continue. ⌛ How to resolve this issue?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 credits. 🚦 How do rate 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 see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (11)
✨ 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 |
|
@Shadow-MMN Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
2 participants
What changed
?pageSize,?streamId, and?sincequery parameters toGET /api/eventsgetGlobalEvents()andcountAllEvents()ineventHistory.tsto support the new filters with AND compositionpageSize,streamId, andsincefields tolistEventsQuerySchemainschemas.ts(keptlimitas a backwards-compatible alias)Testing done
Related issues
Closes #380
Checklist