Fix: Add new Pages to Crypto Dashboard
Closes #217
Summary
This PR implements the missing Statistics and Transaction pages for the Crypto Dashboard template, addressing the core functionality gaps identified in issue #217.
The Statistics page now provides comprehensive portfolio returns analysis with base 100 normalization, allowing users to compare past returns of all coins in their wallet with flexible date range selection. The Transaction page has been completely redesigned with enhanced management capabilities, search/filter functionality, and transaction analytics.
Changes Made
Statistics Page Enhancements
- [x] Implemented past returns visualization with base 100 normalization
- [x] Added flexible date range selection with preset options (1M, 3M, 6M, 1Y, 2Y, All, Custom)
- [x] Created interactive asset selection for comparing individual coins or portfolio performance
- [x] Added performance summary cards showing portfolio metrics and best performing assets
- [x] Integrated advanced portfolio analytics with allocation breakdown, performance metrics, and risk analysis
Transaction Page Improvements
- [x] Fixed duplicate class definitions in original implementation
- [x] Added comprehensive transaction management with add, edit, and delete capabilities
- [x] Implemented search and filter functionality by type, asset, date, and text search
- [x] Created transaction analytics dashboard with summary statistics
- [x] Enhanced add transaction dialog with validation and real-time calculations
- [x] Added sorting capabilities for all table columns
- [x] Implemented export functionality framework
New Components
- [x] Created PortfolioAnalytics component with comprehensive financial metrics
- [x] Added AssetComparisonChart component for normalized returns comparison
- [x] Implemented risk metrics including Sharpe ratio, max drawdown, and Value at Risk
- [x] Added asset correlation analysis for portfolio diversification insights
@mad-moo
You may need to add faker to the list of dependencies in meta.json.
Thank you!
@Sn3llius can you have a look at this? Is this what you had in mind?
@iwr-redmond I'd do this now
If @Sn3llius is unavailable this PR should be reviewed by the core contributors instead.
Is there any update on reviewing this PR?