How turnbula/masterapi works
MasterAPI is an ASP.NET Core API for activity resources. A client calls activity endpoints, the controller validates categories and delegates retrieval or creation to the activity service, which uses the database access layer to query or update SQL Server and returns DTO-shaped results. Startup registers dependencies and maps controllers. The graph preserves listing, latest-activity, random category selection, count updates, and creation capabilities. Configuration paths are inferred from the sampled configuration reads; unsampled database schema details are not expanded.
Components 9
API Runtime
- API Host
MasterAPI/Program.cs - Startup Configuration
MasterAPI/StartUp.cs - Runtime Configuration
MasterAPI/appsettings.json
Activity Domain
- Activities Controller
MasterAPI/Activities/Controllers/ActivitiesController.cs - Activity Service
MasterAPI/Activities/Services/ActivityService.cs - Activity Contracts
MasterAPI/Activities/Models/ActivityDto.cs
Persistence
- SQL Data Access
MasterAPI/Config/MasterDbContext.cs - SQL Database
Other components
- API Client
Connections 11
- API Client → Activities Controller: calls endpoints
- API Host → Startup Configuration: starts runtime
- Startup Configuration → Activities Controller: maps routes
- Startup Configuration → Activity Service: registers service
- Runtime Configuration → Activities Controller: supplies categories
- Runtime Configuration → Activity Service: supplies connection
- Activities Controller → Activity Service: delegates activity
- Activity Service → SQL Data Access: executes queries
- SQL Data Access → SQL Database: reads and writes
- Activity Service → Activity Contracts: builds results
- Activities Controller → API Client: returns results