How ensiasi/serverapi works
TestApi is a minimal ASP.NET Core API for deployment practice. Its runtime workflow is HTTP requests entering the minimal endpoint mappings in Program.cs: root and health return status information, while notes requests read or mutate an in-memory list. Swagger UI is also enabled. The repository has no separate domain, persistence, or service layer; the mappings, validation, and note state all live in the single source file. Relationships shown are limited to those visible in Program.cs and the README.
Main entry points: Program.cs Endpoint Mappings
Components 7
HTTP API
- Endpoint Mappings
Program.cs - Liveness Greeting
Program.cs - Health Check
Program.cs - Notes Endpoints
Program.cs
In-memory State
- In-memory Notes
Program.cs
API Exploration
- Swagger UI
Program.cs
Other components
- HTTP Client
Connections 6
- HTTP Client → Endpoint Mappings: sends requests
Program.cs - Endpoint Mappings → Liveness Greeting: maps route
Program.cs - Endpoint Mappings → Health Check: maps route
Program.cs - Endpoint Mappings → Notes Endpoints: maps routes
Program.cs - Notes Endpoints → In-memory Notes: reads and updates
Program.cs - Endpoint Mappings → Swagger UI: enables UI
Program.cs