How mahmmuod/reactivities works
Main Components
• Client-App (React SPA)
– Components: App.tsx, Router, features/activities, activityStore (MobX), agent.ts (HTTP client).
• API Layer (ASP.NET Core Web API)
– Controllers: ActivitiesController, WeatherForecastController, BaseApiController.
– Startup & Program (DI setup, middleware, routing).
– Extensions: ApplicationServiceExtensions for wiring Application & Persistence.
• Application Layer
– Use-case handlers (Create, Delete, Details, Edit, List).
– Core mapping profiles (AutoMapper).
• Domain Layer
– Entities: Activity.
– Domain abstractions.
• Persistence Layer
– EF Core DataContext, migrations, seed data.
– SQLite database file (reactivities.db).
• External Services
– Browser, Network, File System (SQLite .db), Development settings.
Relationships & Data Flows
• Browser → React SPA → HTTP requests via agent.ts → API endpoints.
• API Controllers → Mediator → Application handlers → Domain models.
• Application handlers → Persistence (EF Core) → SQLite DB.
• Persistence returns data → AutoMapper maps to DTOs → Controllers return JSON → React updates store/UI.
Architectural Patterns
• Clean Architecture / Layered Architecture:
– Outer layers (UI, API, Persistence) depend inward on Application and Domain.
• CQRS-style use cases in Application.
• Dependency Injection configured in Startup.
• AutoMapper for object mapping.
• MobX for client-side state management.
• React Router for client navigation.