How robintty/personalfinancedashboard works
Project type and purpose
• This is a full-stack personal finance dashboard application
• Frontend: React + TypeScript single-page app communicating via GraphQL
• Backend: .NET Core GraphQL API with layered architecture (Core, Infrastructure, DataImport, ThirdPartyDataProviders)
• Database: relational store managed via Entity Framework Core migrations
• External services: banking and payment providers (e.g., GoCardless)
File-structure analysis
• Top level
– deployment/docker-compose.yml orchestrates API, database, possibly mock servers
– docs/docusaurus holds documentation site built with Docusaurus
• src/client
– React/TypeScript code, GraphQL code-gen, Storybook config, mockServiceWorker for local testing
– Components, modals, routes, utility functions, theme definitions
• src/server
– RobinTTY.PersonalFinanceDashboard.API: ASP.NET Core GraphQL endpoint with resolvers for queries/mutations
– Core: domain models (Account, Transaction, etc.)
– Infrastructure: ApplicationDbContext, EF Core entities, repositories, migrations
– DataImport: ETL-like modules to import spreadsheets (e.g., Etoro importer)
– ThirdPartyDataProviders: connectors to external APIs (GoCardless, etc.)
README insights
• Early-stage proof-of-concept for consolidating bank accounts, credit cards, investments
• UX emphasis, budgeting tools, spending analytics
• Architecture section in docs indicates intent to document layers