feat(analytics): export usage data#178
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (7)
📝 WalkthroughWalkthroughAdds analytics export feature allowing users to export session usage data (token counts, session aggregates) as CSV or JSON, filtered by date range and model type. Includes argument parsing, export aggregation and serialization logic, CLI command ChangesAnalytics Usage Export
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Suggested reviewers
Poem
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
ESLint skipped: no ESLint configuration detected in root package.json. To enable, add 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
Extracts the analytics export implementation for #139 from the broader desktop/analytics PR #172 into a focused standalone PR.
Changes:
/analytics exporthandling in the CLI.Closes #139
Validation
npm run test:unit -- --match analytics— passed; test runner reported all 535 unit tests passed.Scope note
This PR intentionally excludes the unrelated desktop/Tauri packaging changes from #172.
Summary by CodeRabbit
New Features
Chores