Expected Return Date Picker
Component Detail
Description
Reusable date selection widget used within the pause activation flow to capture an optional expected return date. Enforces future-only date selection and formats the date for display and storage.
expected-return-date-picker
Summaries
The Expected Return Date Picker is a reusable input component that captures when a paused peer mentor plans to return to active duty. By enforcing future-only date selection and providing a consistent interaction pattern, the organization collects reliable scheduling data that coordinators can use for proactive workforce planning. This data reduces reactive scheduling gaps and helps program managers allocate substitute coverage in advance. As a shared component used across multiple pause-related features, it also reduces development cost by avoiding duplication and ensures a consistent, accessible user experience throughout the application.
This shared, low-complexity widget has no declared dependencies, making it a safe early-delivery item that unblocks the `pause-activation-screen` which depends on it. It is reusable across any future flow that requires future-date capture, offering long-term value beyond its current use case. Testing requirements are straightforward: validate that past dates are rejected, that cleared state resets correctly, and that both `formatForDisplay` and `formatForStorage` produce the expected output formats. Since it is shared, any changes to its interface or validation behavior must be coordinated with all consuming components.
Deliver and stabilize this early to unblock downstream screen integration work.
Stateful Flutter widget exposing `selectDate(minDate)`, `clearSelection()`, `getSelectedDate()`, `formatForDisplay(date)`, and `formatForStorage(date)`. The `minDate` parameter passed to `selectDate` enforces the future-only constraint by setting it to `DateTime.now()` or a caller-specified floor. `formatForDisplay(date)` returns a locale-aware human-readable string. `formatForStorage(date)` returns an ISO 8601 string suitable for API submission.
The widget holds selected date in local state; `clearSelection()` nullifies it and updates the UI. No data model dependencies — this is a pure UI utility. Since it is shared, avoid coupling internal implementation to any specific feature's state management; consumers should bind `getSelectedDate()` to their own provider or controller.
Responsibilities
- Render accessible date picker with future-date constraint
- Format selected date for API submission
- Allow clearing/resetting the return date
Interfaces
selectDate(minDate)
clearSelection()
getSelectedDate()
formatForDisplay(date)
formatForStorage(date)