auto-claude: 025-add-a-unified-stats-dashboard-endpoint-to-eliminat #82
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…syncio.gather - Added asyncio import for parallel query execution - Implemented /stats/dashboard endpoint that fetches all stats concurrently - Uses asyncio.gather to execute 6 stats queries in parallel: * get_overview_stats * get_messages_by_day * get_messages_by_channel * get_trust_stats * get_api_usage_stats * get_translation_metrics - Returns unified dashboard response with all statistics - Includes response caching and proper authentication - Added comprehensive tests for endpoint structure and concurrency
…shboard endpoint - Added collection_id: Optional[UUID] = Query(None) parameter to get_dashboard_stats - Parameter follows existing pattern for optional query parameters - Enables collection-specific dashboard filtering (filtering logic to be implemented)
… response Added DashboardData interface that combines StatsOverview, MessagesByDay[], MessagesByChannel[], and TrustStats to match the backend /stats/dashboard endpoint response schema. Follows existing patterns with JSDoc comments and snake_case naming. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Added statsApi.dashboard(collectionId?: string) method that calls /api/stats/dashboard with optional collection_id parameter. - Imported DashboardData type from types.ts - Added JSDoc documentation following existing patterns - Method accepts optional collectionId string parameter - Passes collection_id as query param when provided - Returns Promise<DashboardData> with unified dashboard statistics This method enables the frontend to fetch all dashboard data in a single API call, eliminating the waterfall of separate stats requests. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Fixes: - Changed backend field name from 'trust' to 'trust_stats' for consistency - Added ApiUsageStats and TranslationMetrics schemas to backend - Added response_model=DashboardResponse to dashboard endpoint - Updated backend tests to expect 'trust_stats' field - Added ApiUsageStats and TranslationMetrics TypeScript interfaces - Updated DashboardData interface with api_usage and translation_metrics fields Verified: - All Python files pass syntax validation - Backend schema imports successfully - All field names now match between backend and frontend - Response validation enabled via response_model parameter QA Fix Session: 1 Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
maynetee
deleted the
auto-claude/025-add-a-unified-stats-dashboard-endpoint-to-eliminat
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The DashboardPage (
frontend/src/features/dashboard/dashboard-page.tsx) makes 5-7 independent API calls on mount: channels list, collections list, stats overview, messages-by-day, messages-by-channel, trust stats, and optionally collection-specific stats. While React Query parallelizes independent calls, the channels/collections queries must complete first (they gate theenabledflag on downstream queries), creating a 2-stage waterfall: stage 1 loads channels+collections, stage 2 fires 3-4 stats queries.