How migueloliveiradev/living works
Main Components
• Front End: Represent the Living.WebAPP, which is built on Nuxt 3 and Vue.js. This component handles the user interface and client-side logic, using PrimeVue for UI components and integrating with ESLint, TypeScript, and OpenAPI TypeScript for type-generation.
• Back End – API: Represent the Living.WebAPI project, built on ASP.NET Core. This project includes controllers (e.g., AuthController, PostController) that expose REST endpoints. Include aspects such as middleware (for authentication, exception handling) and documentation provided through Swagger.
• Domain Layer: Represent the Living.Domain project that contains core business logic, aggregates, domain entities (e.g., Post, User, Group), value objects, and domain constants. This layer enforces business rules and encapsulates domain models.
• Infrastructure: Represent the Living.Infraestructure project to show how persistence is managed. This includes the EF Core context, database configurations (targeting PostgreSQL), repositories (e.g., PostRepository, UserRepository), migrations, and identity services.
Relationships and Data Flow Between Components
• The Application layer communicates with the Domain layer to execute business logic and then coordinates with the Infrastructure layer (via the Unit of Work and Repository patterns) for database operations.
• External services such as the PostgreSQL database (managed via Entity Framework Core) should be shown connected to the Infrastructure layer.
• Authentication flows: Highlight the use of ASP.NET Core Identity in the API and Infrastructure layers, and indicate any integrations with token services (as seen in ITokenService and related handlers/services) for handling authentication.
Architectural Patterns and Technologies
• Mediator Pattern: Indicate the use of MediatR for decoupling and handling operations.
• DI (Dependency Injection): Although implicit in the modular design, indicate that most components are wired together through .NET’s dependency injection.
• ORM: Highlight that EF Core works as the ORM connecting to PostgreSQL.
• Identity and Security: Call out the ASP.NET Core Identity integration for user management.
• Testing: Optionally add a note that robust unit and integration testing is covered by xUnit, Testcontainers, and other testing frameworks.
Additional Notes
• Since the project also includes tests and tooling modules, include a small section (if space permits) that shows how tests validate the core components.