1.7 KiB
1.7 KiB
Recommended tasks for the next sprint
-
In the mobile applications, since the structure is now finalized (at least for the existing features), we need to strictly follow best practices while coding:
- Break down large widgets into smaller, reusable widgets
- Add doc comments where necessary to improve readability and maintainability
- Remove overly complicated or unnecessary logic introduced by AI and simplify where possible
- Adhere to the design system and remove all hard-coded colors and typography, using shared tokens instead
-
Improvement points
- apps/mobile/packages/features/client/client_coverage/lib/src/data/repositories_impl/coverage_repository_impl.dart
- Fix the location field in CoverageShiftRole to use the correct fallback logic.
- line 125 remove redundant location values.
- Need to clarify the difference b/w
case dc.ApplicationStatus.ACCEPTEDandcase dc.ApplicationStatus.CONFIRMED. - Update the dataconnect docs.
- Track
latandlngin the staff preferred work locations (for now we are only storing the name). - Remove "Up Next (x)" counter from orders list in client app as it is confusing, becase the tab already has a badge showing the number of the upcoming orders.
final String status;inOrderItemmake it an enum.- /// Date of the shift (ISO format). final String date; make this in the DateTime format instead of string.
- in
view_orders_cubit.dartcombine the logic of_calculateUpNextCountand_calculateTodayCountinto a single function that calculates both counts together to avoid redundant filtering of orders. - In places api call in the when the api's not working we need to show a proper error message instead of just an empty list.