Wire real-time field validation and error display in EditContactScreen
epic-contact-detail-and-edit-supporting-ui-task-015 — Integrate contact-form-validator with EditContactScreen so that each AppTextField calls its corresponding validator on change and on blur. Display field-level error messages below each field using the plain-language error display pattern. Disable the save button when any field has a validation error. Ensure error messages use org-label system for terminology consistency.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 3 - 413 tasks
Can start after Tier 2 completes
Implementation Notes
Implement a two-phase validation strategy: (1) 'touched' flag per field set on first blur, (2) error displayed only if field is touched OR a save attempt has been made. This prevents all fields showing errors immediately on screen load. Store validation state in ContactEditFormNotifier alongside field values — call notifier.setFieldValue(field, value) on change and notifier.touchField(field) on blur. The notifier computes isFormValid as a derived getter: true only when all touched fields (or all fields after save attempt) are valid.
Pass the computed error string (resolved from org-labels) directly to AppTextField's errorText parameter. For WCAG compliance, verify that AppTextField wraps errorText in a Semantics widget with error semantics — if not, wrap it manually.
Testing Requirements
Widget tests: (1) enter invalid email → assert error text visible below email field; (2) fix email → assert error text gone and save button enabled; (3) clear required name field → blur → assert 'required' error shown; (4) assert save button disabled when any error active; (5) assert error text uses org-label resolved string (inject mock org-label provider). Unit tests: ContactEditFormNotifier.validateField dispatches correct ValidationResult for each field type. All tests use mock contact-detail-service and mock org-label provider via Riverpod overrides.
The encrypted-field-display confirmation dialog adds interaction steps that may frustrate coordinators who access sensitive fields frequently, leading to requests to bypass the flow or skip read-receipt logging, which would violate Blindeforbundet's compliance requirements.
Mitigation & Contingency
Mitigation: Design the confirmation dialog to be as minimal as possible (one clear sentence, single confirm action) and ensure it does not reappear for the same field within a single screen session. Validate the UX with Blindeforbundet coordinators during the TestFlight pilot before finalising.
Contingency: If coordinators raise strong objections, escalate to Blindeforbundet's data protection officer to determine whether a lighter confirmation pattern (e.g., biometric confirmation instead of dialog) satisfies their compliance obligation.
The activity-history-list infinite scroll requires paginated Supabase queries. Contacts with hundreds of activities (e.g., an HLF peer mentor with 380 annual registrations) could cause slow page loads or memory pressure on older devices if pagination boundaries are set too large.
Mitigation & Contingency
Mitigation: Use a page size of 20 records with cursor-based pagination. Implement list item recycling using Flutter's ListView.builder. Benchmark memory usage with 400+ item simulation on a low-end test device before TestFlight release.
Contingency: If performance degrades on older devices, reduce page size to 10 and add a time-window filter (last 30 days, last 6 months, all) so the default view loads a manageable record count for most coordinators.
The cognitive load rule engine (from the Cognitive Accessibility feature) mandates no more than 7 fields per screen section. If a contact model has more than 7 editable fields, the edit-contact-screen layout must be split into sections, adding complexity not accounted for in the initial scope.
Mitigation & Contingency
Mitigation: Audit the full contact field list from all four organisations before implementation. Group fields into logical sections (personal info, contact details, affiliation) so no single section exceeds 7 fields. Use the cognitive-load-rule-engine component if it is already delivered by the Cognitive Accessibility feature.
Contingency: If the rule-engine component is not yet available, implement a simple manual section layout with accordion-style expansion for less-frequently edited fields to stay within the 7-field guideline without blocking delivery.