Extend core attendance statuses#323
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (9)
Walkthrough데이터베이스 스키마가 부울 기반 Changes
Sequence DiagramsequenceDiagram
participant Client
participant Controller
participant Service
participant Repository
participant Database
Client->>Controller: PATCH /attendance (status=LATE)
Controller->>Service: setAttendance(date, userIds, LATE)
Service->>Service: isTeamScoped(userRole, team)
Service->>Service: resolveEffectiveTeam(...)
Service->>Repository: upsertBatchByMeetingId(meetingId, userIds, "LATE")
Repository->>Database: UPDATE attendance_records SET status='LATE'
Database-->>Repository: success
Repository-->>Service: rows affected
Service->>Repository: getStatusMap(date)
Repository->>Database: SELECT userId, status FROM attendance_records
Database-->>Repository: [(userId, LATE), ...]
Repository-->>Service: Map<Long, AttendanceStatus>
Service->>Service: countStatus(users, statusMap, PRESENT/LATE/etc)
Service-->>Controller: DaySummaryResponse
Controller-->>Client: 200 OK {present, late, preArranged, absent}
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment Tip CodeRabbit can generate a title for your PR based on the changes.Add |
📌 연관된 이슈
✨ 작업 내용
💬 리뷰 요구사항(선택)
Summary by CodeRabbit
릴리스 노트
New Features
Chores