How aarhusuniversitet/webapicase works
This is a small ASP.NET Core product API. A client requests the products endpoints; the controller queries SQLite and returns product records. Program.cs configures the database connection and maps controller routes. The README says API calls are defined in ProductsController.cs and that IProductManager.cs is not currently used. The graph reflects the shown source; it does not infer write operations or behavior from unsampled files.
Main entry points: ProductsController.cs Products controller · Program.cs Application host · app.db SQLite database · Product.cs Product record
Components 6
API runtime
- Application host
Program.cs - Products controller
Controllers/ProductsController.cs - SQLite database
app.db
Product domain
- Product record
Product.cs - Unused manager contract
Logic/IProductManager.cs
Other components
- API client
Connections 6
- API client → Products controller: requests products
README.md - Application host → Products controller: maps routes
Program.cs - Application host → SQLite database: opens and initializes
Program.cs - Products controller → SQLite database: queries
Controllers/ProductsController.cs - Products controller → Product record: creates records
Controllers/ProductsController.cs - Unused manager contract → Product record: uses type
Logic/IProductManager.cs