How vlikcc/mebtoplantitakip works
Project Type and Purpose
• This is a full-stack meeting-tracking application for the Turkish Ministry of Education.
• Backend: ASP.NET Core RESTful API, Entity Framework Core, SQL Server.
• Frontend: React single-page app built with Create React App.
Main Components
a. Presentation Layer
• Web Client (Browser) running React SPA (meb-toplanti-takip/src)
• UI Components, Routes, Contexts (AuthContext, ProtectedRoute)
b. API Layer
• ASP.NET Core Web API (Controllers/)
• Endpoints: MeetingsController, AttendeesController, LocationsController, UsersController, QrCodeController
c. Business Logic Layer
• Services (Services/): MeetingService, AttendeeService, LocationService, UserService, QrCodeService, FileService
d. Data Access Layer
• Entity Framework Core DbContext (DbContexts/MebToplantiTakipContext)
• Migrations (Migrations/), Entities (Entities/), DTOs (Dtos/)
e. Persistence
• SQL Server Database
• File storage on disk under wwwroot/Uploads for meeting documents and generated QR codes
f. External/Infrastructure
• Docker (Dockerfile, .dockerignore)
• Configuration: appsettings.json (including connection string), launchSettings.json
• Development tools: .vscode, dotnet-tools.json
Relationships and Data Flows
• Browser → HTTP(S) calls → React SPA → Axios or fetch calls → API endpoints
• API Controller receives request → injects appropriate Service → Service uses DbContext → EF Core queries SQL Server → returns Entities → mapped to DTOs → returned as JSON
• File upload/download flows through FileService → saves to/reads from wwwroot/Uploads
• QrCodeService generates codes on demand, stored or streamed to client
• Authentication state handled in React (AuthContext) and ASP.NET Core middleware (e.g., JWT or cookie auth)
Architectural Patterns and Principles
• Layered architecture (Presentation → API → Business → Data)
• Separation of concerns (Controllers only handle HTTP, Services only implement business logic, DbContext for persistence)
• Dependency injection for Services and DbContext in Program.cs
• DTOs to decouple internal Entities from API contracts
• Code-first migrations for database schema evolution
Technologies and Frameworks to Annotate
• Frontend: React, Context API, React Router, Axios (or fetch), Create React App
• Backend: ASP.NET Core 6.0, Entity Framework Core, SQL Server, Docker
• Infrastructure: Dockerfile, .dockerignore, appsettings.json