How giorgibokuchava/todoapi works
TodoApi is a small ASP.NET Core REST backend for managing ToDo items. An HTTP client reaches the mapped API controllers, which perform asynchronous CRUD operations through TodoContext and return DTOs; updates include ID checks and concurrency handling. Program.cs configures the in-memory EF Core store and, in Development, OpenAPI/Swagger. The repository also includes a standalone weather-forecast endpoint. The main workflow is supported by sampled controller, model, and startup code; Swagger setup is documented in startup code, but its internal runtime is framework-provided.
Main entry points: Program.cs App startup · TodoItemsController.cs ToDo controller · TodoContext.cs EF context · WeatherForecastController.cs Weather endpoint
Components 10
API hosting
- App startup
TodoApi/Program.cs - Swagger UI / OpenAPI
TodoApi/Program.cs
API endpoints
- ToDo controller
TodoApi/Controllers/TodoItemsController.cs - Weather endpoint
TodoApi/Controllers/WeatherForecastController.cs - Forecast model
TodoApi/WeatherForecast.cs
ToDo data
- EF context
TodoApi/Models/TodoContext.cs - ToDo entity
TodoApi/Models/TodoItem.cs - ToDo DTO
TodoApi/Models/TodoItemsDTO.cs - In-memory store
Other components
- HTTP client
Connections 10
- HTTP client → App startup: sends HTTP
- App startup → ToDo controller: maps controllers
- App startup → Weather endpoint: maps controllers
- ToDo controller → EF context: queries / saves
- EF context → In-memory store: reads / writes
- ToDo controller → ToDo entity: creates / updates
- ToDo controller → ToDo DTO: maps responses
- Weather endpoint → Forecast model: creates forecasts
- App startup → EF context: registers context
- App startup → Swagger UI / OpenAPI: configures in Development