How justanothercodingirl/shift-planner works
The repository presents Shift Planner as a café/restaurant rostering tool: managers prepare weekly rosters, employees view shifts, submit availability, and swap shifts, subject to rules. The sampled implementation does not yet show those scheduling workflows: the frontend is the stock Vite/React starter, and the backend exposes manager-only employee CRUD. Its visible path is request → controller → service → repositories/entities → database. The README documents intended capabilities, but no schedule, availability, swap, or rule-enforcement modules appear in the tree; unsampled wiring is not inferred.
Main entry points: EmployeeService.php Employee service · EmployeeController.php Employee controller · App.jsx Starter UI · EmployeeResponse.php Employee response
Components 12
Frontend
- Starter UI
frontend/src/App.jsx
Employee API
- Employee controller
backend/src/Controller/EmployeeController.php - Request DTOs
backend/src/Dto/CreateEmployeeRequest.php - Employee response
backend/src/Dto/EmployeeResponse.php - Employee service
backend/src/Service/EmployeeService.php
Employee data
- Employee repository
backend/src/Repository/EmployeeRepository.php - User repository
backend/src/Repository/UserRepository.php - Employee entity
backend/src/Entity/Employee.php - User entity
backend/src/Entity/User.php - Relational database
Other components
- Manager
- Employee
Connections 13
- Manager → Employee controller: manages employees
backend/src/Controller/EmployeeController.php - Employee → Starter UI: uses app
README.md - Starter UI → Employee controller: calls API
- Employee controller → Employee service: delegates
backend/src/Controller/EmployeeController.php - Employee controller → Request DTOs: accepts payloads
backend/src/Controller/EmployeeController.php - Employee controller → Employee response: formats results
backend/src/Controller/EmployeeController.php - Employee service → Employee repository: reads and saves
backend/src/Service/EmployeeService.php - Employee service → User repository: checks email
backend/src/Service/EmployeeService.php - Employee service → Employee entity: creates and updates
backend/src/Service/EmployeeService.php - Employee service → User entity: creates account
backend/src/Service/EmployeeService.php - Employee repository → Relational database: persists employee
backend/src/Repository/EmployeeRepository.php - User repository → Relational database: queries users
backend/src/Repository/UserRepository.php - Employee response → Employee entity: maps entity
backend/src/Dto/EmployeeResponse.php