How artem-pliusnin/reenbit-camp works
This repository is an ASP.NET Core API shell with application messaging contracts and small domain primitives; no business feature or endpoint is implemented in the sampled source. The visible runtime setup builds the web app, enables HTTPS redirection, and exposes Swagger only in development. Application defines MediatR command/query contracts with Result-based responses, while Domain supplies result/error types and a generic repository contract. Persistence and Infrastructure have no sampled runtime implementation, so their wiring and any user-to-result workflow cannot be established.
Main entry points: Result.cs Result types · ICommandHandler.cs Command handlers · IQueryHandler.cs Query handlers · Program.cs Web app
Components 12
API shell
- Web app
Reenbit-camp.backend/Presentation.API/Program.cs - Swagger setup
Reenbit-camp.backend/Presentation.API/Program.cs
Messaging contracts
- Command contracts
Reenbit-camp.backend/Application/Abstractions/Messaging/ICommand.cs - Command handlers
Reenbit-camp.backend/Application/Abstractions/Messaging/ICommandHandler.cs - Query contracts
Reenbit-camp.backend/Application/Abstractions/Messaging/IQuery.cs - Query handlers
Reenbit-camp.backend/Application/Abstractions/Messaging/IQueryHandler.cs
Domain primitives
- Result types
Reenbit-camp.backend/Domain/Shared/Result.cs - Typed result
Reenbit-camp.backend/Domain/Shared/ResultT.cs - Error value
Reenbit-camp.backend/Domain/Shared/Error.cs - Repository contract
Reenbit-camp.backend/Domain/Repositories/IRepository.cs
Other components
- HTTP caller
- MediatR
Connections 10
- HTTP caller → Web app: sends HTTP
- Web app → Swagger setup: registers
- Command contracts → MediatR: extends request
- Query contracts → MediatR: extends request
- Command handlers → MediatR: implements handler
- Query handlers → MediatR: implements handler
- Command handlers → Result types: returns
- Query handlers → Typed result: returns
- Typed result → Result types: inherits
- Result types → Error value: uses