Krow/Krow-workspace
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: Add comments to clarify the need for APPLICATIONSTATUS and SHIFTSTATUS enums in ShiftsRepositoryImpl

Browse Source
This commit is contained in:
Achintha Isuru
2026-02-18 15:42:10 -05:00
parent 535f6ffb1c
commit c4d0d865d7
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
apps/mobile/packages/features/staff/shifts/lib/src/data/repositories_impl/shifts_repository_impl.dart
View File

@@ -15,6 +15,8 @@ class ShiftsRepositoryImpl
// Cache: ApplicationID -> RoleID (For Accept/Decline w/ Update mutation) // Cache: ApplicationID -> RoleID (For Accept/Decline w/ Update mutation)
final Map<String, String> _appToRoleIdMap = {}; final Map<String, String> _appToRoleIdMap = {};
// This need to be an APPLICATION
// THERE SHOULD BE APPLICATIONSTATUS and SHIFTSTATUS enums in the domain layer to avoid this string mapping and potential bugs.
@override @override
Future<List<Shift>> getMyShifts({ Future<List<Shift>> getMyShifts({
required DateTime start, required DateTime start,