ContactSearchWidget
Component Detail
User Interface
medium complexity
mobile
0
Dependencies
0
Dependents
1
Entities
0
Integrations
Description
Dedicated search input component supporting lookup by name and other configured identifiers. Emits query events consumed by the parent screen to filter the displayed contact list in real time or on submission. Handles debounce, clear, and empty-state display.
contact-search-widget
Sources & reasoning
Line 162 explicitly marks contact search as MUST HAVE Phase 1 for all five organisations. Line 291 confirms role-specific views as a core mobile architecture requirement. Line 467 canonically places this feature in the Contacts area taxonomy. MVP target derives from the Phase 1 position in the priority matrix and from line 321 listing contact list as a Phase 1 deliverable.
-
docs/source/likeperson.md · line 162| Basic search (contact og notater) | ✓ | ✓ | ✓ | ✓ | ✓ | MUST | 1 |
-
docs/source/likeperson.md · line 291- Contacts list with role-specific views
-
docs/source/likeperson.md · line 467| contacts | Contacts | Contact List & Search, Contact Detail & Edit, Caregiver & Next-of-Kin |
Responsibilities
- Accept and debounce free-text search input from the user
- Emit search query events to parent ContactListScreen for result filtering
- Display clear button and reset search state on demand
- Show empty-state feedback when no results match the active query
- Support lookup by name and additional identifier fields as configured per organisation
Interfaces
onQueryChange(query: string): void
clearSearch(): void
setPlaceholder(label: string): void
focus(): void