How kassioburgadon/sistemagestao works
SistemaGestao is an ASP.NET Core task-management API. A client sends task requests to the Tarefas controller; the controller validates and maps create/update DTOs, performs CRUD and status/date filtering through the EF Core context, and returns task data or HTTP results. The task entity defines the domain record and status values, while the context exposes its EF set. The README also documents Swagger/OpenAPI. Program configuration and database wiring were not sampled, so those runtime connections are not asserted.
Main entry points: TarefasController.cs Task Endpoints · SistemaGestaoContext.cs EF Context · Program.cs Swagger / OpenAPI · TarefaCreateDto.cs Create DTO
Components 9
API
- Task Endpoints
SistemaGestao/Controllers/TarefasController.cs - Swagger / OpenAPI
SistemaGestao/Program.cs
Task Contracts
- Create DTO
SistemaGestao/Dtos/TarefaCreateDto.cs - Update DTO
SistemaGestao/Dtos/TarefaUpdateDto.cs - Read DTO
SistemaGestao/Dtos/TarefaReadDto.cs
Domain and Data
- Task Entity
SistemaGestao/Models/Tarefa.cs - EF Context
SistemaGestao/Data/SistemaGestaoContext.cs - In-Memory Store
Other components
- API Client
Connections 8
- API Client → Task Endpoints: sends requests
README.md - Task Endpoints → Create DTO: accepts input
SistemaGestao/Controllers/TarefasController.cs - Task Endpoints → Update DTO: accepts input
SistemaGestao/Controllers/TarefasController.cs - Task Endpoints → Read DTO: projects results
SistemaGestao/Controllers/TarefasController.cs - Task Endpoints → EF Context: queries and saves
SistemaGestao/Controllers/TarefasController.cs - EF Context → Task Entity: exposes set
SistemaGestao/Data/SistemaGestaoContext.cs - EF Context → In-Memory Store: uses provider
- API Client → Swagger / OpenAPI: views API docs
README.md