How jagr-ecu/dotnet-react-activities works
This repository implements a social activity platform: users register or log in, discover and manage activities, join or host them, and interact through profiles, follows, photos, and activity comments/chat. The React client routes these experiences and maintains MobX stores; the ASP.NET API dispatches requests into application handlers, which use domain entities and persistence. Photo storage and user identity are behind infrastructure adapters. The README is empty, so feature coverage comes from the file tree; several client-to-API and unsampled handler links remain unverified.
Main entry points: DataContext.cs Entity Framework context · App.tsx Route and session shell · AppUser.cs User and activity entities · Add.cs Photo workflows
Components 25
Web client
- Route and session shell
client-app/src/app/layout/App.tsx - MobX store registry
client-app/src/app/stores/store.ts - Activity screens
client-app/src/features/activities - Profile screens
client-app/src/features/activities/profiles - Login and registration
client-app/src/features/users - HTTP client
client-app/src/app/api/agent.ts
HTTP and realtime API
- Activity and account endpoints
API/Controllers/ActivitiesController.cs - Photo endpoints
API/Controllers/PhotosController.cs - JWT token service
API/Services/TokenService.cs - Realtime chat hub
API/SignalR/ChatHub.cs
Application workflows
- Activity workflows
Application/Activities - Activity comments
Application/Comments - Profiles and follows
Application/Profiles - Photo workflows
Application/Photos/Add.cs - DTO mapping
Application/Core/MappingProfiles.cs
Domain and persistence
- User and activity entities
Domain/AppUser.cs - Activity entity
Domain/Activity.cs - Attendance relation
Domain/ActivityAttendee.cs - Comment entity
Domain/Comment.cs - Photo entity
Domain/Photo.cs - Entity Framework context
Persistence/DataContext.cs
Infrastructure adapters
- Current-user adapter
Infrastructure/Security/UserAccessor.cs - Cloud photo adapter
Infrastructure/Photos/PhotoAccessor.cs
Other components
- Platform user
- Cloudinary service
Connections 34
- Platform user → Route and session shell: uses
client-app/src/app/layout/App.tsx - Route and session shell → Activity screens: routes to
client-app/src/app/layout/App.tsx - Route and session shell → Profile screens: routes to
client-app/src/app/layout/App.tsx - Route and session shell → Login and registration: routes to
client-app/src/app/layout/App.tsx - Route and session shell → MobX store registry: reads session
client-app/src/app/layout/App.tsx - MobX store registry → Activity screens: provides state
- Activity screens → HTTP client: requests data
- Profile screens → HTTP client: requests data
- Login and registration → HTTP client: submits credentials
- Activity and account endpoints → Activity workflows: dispatches commands
API/Controllers/ActivitiesController.cs - Activity and account endpoints → Activity workflows: updates attendance
API/Controllers/ActivitiesController.cs - Photo endpoints → Photo workflows: dispatches photo commands
API/Controllers/PhotosController.cs - JWT token service → User and activity entities: creates claims from
API/Services/TokenService.cs - Realtime chat hub → Platform user: exchanges messages
- Activity workflows → Entity Framework context: reads and writes
Application/Activities/UpdateAttendance.cs - Activity workflows → Current-user adapter: gets current user
Application/Activities/UpdateAttendance.cs - Photo workflows → Entity Framework context: reads and writes
Application/Photos/Add.cs - Photo workflows → Current-user adapter: gets current user
Application/Photos/Add.cs - Photo workflows → Cloud photo adapter: uploads photo
Application/Photos/Add.cs - Cloud photo adapter → Cloudinary service: stores image
- Current-user adapter → User and activity entities: resolves username
- Entity Framework context → User and activity entities: persists
Persistence/DataContext.cs - Entity Framework context → Activity entity: persists
Persistence/DataContext.cs - Entity Framework context → Attendance relation: persists
Persistence/DataContext.cs - Entity Framework context → Comment entity: persists
Persistence/DataContext.cs - Entity Framework context → Photo entity: persists
Persistence/DataContext.cs - DTO mapping → Activity entity: maps
Application/Core/MappingProfiles.cs - DTO mapping → User and activity entities: maps
Application/Core/MappingProfiles.cs - DTO mapping → Comment entity: maps
Application/Core/MappingProfiles.cs - Activity comments → Entity Framework context: reads and writes
Application/Comments/Create.cs - Profiles and follows → Entity Framework context: reads and writes
Application/Profiles/Edit.cs - Activity entity → Attendance relation: has attendees
Domain/Activity.cs - Activity entity → Comment entity: has comments
Domain/Activity.cs - User and activity entities → Photo entity: has photos
Domain/AppUser.cs