How neto-santana-22/korpis works
Korpis is a finance-management SPA and REST API for client records, Pix charges, and financial metrics. The main workflow is user sign-in, navigation to client or charge management, API requests, persistence, and dashboard review; charge operations also include Pix generation and simulated payment/cancellation. The README describes JWT/REST and PostgreSQL, while sampled backend persistence uses Entity Framework Core. Edges reflect sampled calls, SOURCE INDEX references, or README claims; unsampled capabilities and integrations are shown only where documented.
Main entry points: api.ts HTTP client · App.tsx App navigation · AppDbContext.cs Database context · ChargesManager.tsx Charge manager
Components 19
Web application
- App navigation
frontend/src/App.tsx - Login view
frontend/src/components/LoginView.tsx - Client manager
frontend/src/components/ClientsManager.tsx - Charge manager
frontend/src/components/ChargesManager.tsx - Dashboard view
frontend/src/components/DashboardView.tsx - HTTP client
frontend/src/services/api.ts - Currency formatters
frontend/src/utils/formatters.ts
API workflows
- Authentication endpoint
backend/Controllers/AuthController.cs - Client endpoints
backend/Controllers/ClientsController.cs - Charge endpoints
backend/Controllers/ChargesController.cs - Dashboard endpoint
backend/Controllers/DashboardController.cs
Domain and services
- Client repository
backend/Infrastructure/Repositories/ClientRepository.cs - Charge repository
backend/Infrastructure/Repositories/ChargeRepository.cs - Mock Pix service
backend/Infrastructure/Services/MockPaymentService.cs - Client records
backend/Domain/Entities/Client.cs - Charge records
backend/Domain/Entities/Charge.cs
Persistence
- Database context
backend/Infrastructure/Data/AppDbContext.cs - PostgreSQL
Other components
- Finance user
Connections 24
- Finance user → App navigation: uses
README.md - App navigation → Login view: shows when signed out
frontend/src/App.tsx - App navigation → Client manager: selects
frontend/src/App.tsx - App navigation → Charge manager: selects
frontend/src/App.tsx - App navigation → Dashboard view: selects
frontend/src/App.tsx - Login view → HTTP client: requests login
README.md - Client manager → HTTP client: requests clients
frontend/src/components/ClientsManager.tsx - Charge manager → HTTP client: requests charges and clients
frontend/src/components/ChargesManager.tsx - Dashboard view → HTTP client: requests metrics
frontend/src/components/DashboardView.tsx - Charge manager → Currency formatters: formats amounts
frontend/src/components/ChargesManager.tsx - HTTP client → Authentication endpoint: sends REST requests
README.md - HTTP client → Client endpoints: sends REST requests
README.md - HTTP client → Charge endpoints: sends REST requests
README.md - HTTP client → Dashboard endpoint: sends REST requests
README.md - Client endpoints → Client repository: uses repository
backend/Controllers/ClientsController.cs - Charge endpoints → Charge repository: uses repository
backend/Controllers/ChargesController.cs - Charge endpoints → Mock Pix service: invokes payment service
backend/Controllers/ChargesController.cs - Dashboard endpoint → Database context: queries metrics
backend/Controllers/DashboardController.cs - Client repository → Database context: reads and writes
backend/Infrastructure/Repositories/ClientRepository.cs - Charge repository → Database context: reads and writes
backend/Infrastructure/Repositories/ChargeRepository.cs - Database context → PostgreSQL: persists data
README.md - Client repository → Client records: manages
backend/Infrastructure/Repositories/ClientRepository.cs - Charge repository → Charge records: manages
backend/Infrastructure/Repositories/ChargeRepository.cs - Mock Pix service → Charge records: operates on
backend/Infrastructure/Services/MockPaymentService.cs