From c4d0d865d733866393a7a7f187e9a59a6eb88cb5 Mon Sep 17 00:00:00 2001
From: Achintha Isuru <achinthaisuru444@gmail.com>
Date: Wed, 18 Feb 2026 15:42:10 -0500
Subject: [PATCH] feat: Add comments to clarify the need for APPLICATIONSTATUS
 and SHIFTSTATUS enums in ShiftsRepositoryImpl

---
 .../lib/src/data/repositories_impl/shifts_repository_impl.dart  | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/apps/mobile/packages/features/staff/shifts/lib/src/data/repositories_impl/shifts_repository_impl.dart b/apps/mobile/packages/features/staff/shifts/lib/src/data/repositories_impl/shifts_repository_impl.dart
index 8be4f612..4428a780 100644
--- a/apps/mobile/packages/features/staff/shifts/lib/src/data/repositories_impl/shifts_repository_impl.dart
+++ b/apps/mobile/packages/features/staff/shifts/lib/src/data/repositories_impl/shifts_repository_impl.dart
@@ -15,6 +15,8 @@ class ShiftsRepositoryImpl
   // Cache: ApplicationID -> RoleID (For Accept/Decline w/ Update mutation)
   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
   Future<List<Shift>> getMyShifts({
     required DateTime start,