How ryvarma7/leaveflow works
LeaveFlow is a leave-management platform spanning employee requests, manager/HR decisions, peer coverage, entitlement accounting, and payroll impact. Employees use the React app to submit and track requests; the Spring API coordinates validation and workflow, persists decisions and ledger changes, and exposes role-specific queues and statements. The README documents automated SLA escalation, conflict/capacity checks, and HR administration as additional capabilities. Source excerpts are partial, so some documented subsystem wiring is shown only where supported; unsampled features are represented without speculative call chains.
Main entry points: api.ts REST client · LeaveWorkflowService.java Request workflow · App.tsx Role-based app · LeaveRequestRepository.java Data repositories
Components 23
Web application
- Role-based app
frontend/src/App.tsx - Session context
frontend/src/context/AuthContext.tsx - Employee leave
frontend/src/pages/employee/ApplyLeave.tsx - Manager decisions
frontend/src/pages/manager/ManagerQueue.tsx - HR review
frontend/src/pages/hr/HrRequestReview.tsx - Payroll views
frontend/src/pages/hr/HrPayroll.tsx - REST client
frontend/src/lib/api.ts
API and identity
- JWT authentication
backend/src/main/java/com/leaveflow/service/JwtService.java - Leave endpoints
backend/src/main/java/com/leaveflow/web/controller/LeaveRequestController.java - Coverage endpoints
backend/src/main/java/com/leaveflow/web/controller/CoverageController.java - Payroll endpoints
backend/src/main/java/com/leaveflow/web/controller/PayrollController.java - HR administration
backend/src/main/java/com/leaveflow/web/controller/HrController.java
Leave workflow
- Request workflow
backend/src/main/java/com/leaveflow/service/LeaveWorkflowService.java - Five-state machine
backend/src/main/java/com/leaveflow/domain/statemachine/LeaveStateMachine.java - SLA escalation
backend/src/main/java/com/leaveflow/service/EscalationScheduler.java - Leave calculations
backend/src/main/java/com/leaveflow/domain/calculator/PayCalculator.java
Coverage and balances
- Peer coverage
backend/src/main/java/com/leaveflow/service/CoverageService.java - Balance ledger
backend/src/main/java/com/leaveflow/service/BalanceService.java - Dashboard metrics
backend/src/main/java/com/leaveflow/web/controller/DashboardController.java
Persistence
- Data repositories
backend/src/main/java/com/leaveflow/repository/LeaveRequestRepository.java - PostgreSQL
Other components
- Employee / HR
- Web browser
Connections 30
- Employee / HR → Web browser: uses
- Web browser → Role-based app: opens
- Role-based app → Session context: provides session
- Role-based app → Employee leave: routes
- Role-based app → Manager decisions: routes
- Role-based app → HR review: routes
- Role-based app → Payroll views: routes
- Employee leave → REST client: requests
- Manager decisions → REST client: requests
- HR review → REST client: submits actions
- Payroll views → REST client: fetches statement
- REST client → Leave endpoints: HTTP requests
- REST client → Coverage endpoints: HTTP requests
- REST client → Payroll endpoints: HTTP requests
- REST client → HR administration: HTTP requests
- Leave endpoints → Request workflow: submits decisions
- Coverage endpoints → Peer coverage: delegates coverage
- Request workflow → Peer coverage: declines overlaps
- Request workflow → Leave calculations: calculates pay
- Request workflow → Balance ledger: reserves balance
- Request workflow → Five-state machine: applies transitions
- SLA escalation → Request workflow: escalates due requests
- Leave endpoints → Leave calculations: calculates preview
- Request workflow → Data repositories: persists requests
- Peer coverage → Data repositories: reads and writes assignments
- Balance ledger → Data repositories: writes ledger
- Data repositories → PostgreSQL: reads and writes
- Dashboard metrics → Data repositories: reads metrics
- Session context → REST client: authenticates
- Leave endpoints → JWT authentication: uses JWT identity