How dontnod/web-app-starter works
Project Type and Purpose
• This is a full-stack web application boilerplate combining a React SPA client and a .NET 8 backend.
• It demonstrates authentication and authorization via Azure AD and MSAL, exposes a To-Do API, and uses a Clean/CQRS architecture with EF Core for persistence.
File Structure
• Top-level “src” folder subdivided into:
• Api: ASP.NET Core Web API, controllers, middleware, security filters, configuration.
• Application: business logic layer with CQRS (Commands, Queries), cross-cutting behaviors (logging, validation, performance, exception handling).
• Domain: entities, value objects, domain events.
• Infrastructure: EF Core DbContext, migrations, interceptors, domain-event dispatching.
• Client: React/Vite SPA, MSAL authentication, API clients, components, hooks, routes.
• Tests folder for functional end-to-end tests against the API and database in memory.
• Dev-ops/config files (Dockerfile, docker-compose, GitHub workflows, devcontainer) for local/dev/prod environments.
README Insights
• React SPA obtains JWT ID Token via MSAL from Azure AD, calls the To-Do .NET API.
• Database migrations using EF CLI.
• Docker-compose orchestration of SPA, API, and DB.
• Dev Container support for consistent dev environment.
Detail
• Mediator pipeline behaviors (logging, validation, performance).
• Interceptors for domain-event dispatch before/after saving entities.
• Environment configurations (appsettings, .env) feeding into Docker compose.
• Dev Container boundary if illustrating developer workflows.