/**
 * One Formik object covering **both** records this screen edits: the account and
 * the volunteer profile. They are saved through two endpoints but asked for as
 * one form, which is why the values are combined here.
 */
export interface CombinedFormValues {
  email: string;
  phone_number: string;
  country_code: string;
  password: string;
  first_name: string;
  last_name: string;
  documents: File[];
  nickname: string;
  occupation: string;
  experience_field: string;
  /* Numeric: filled from `interest_display[].id` and from `/choices/`, both
     integers, and submitted as JSON (not FormData) under `interest_ids`, so
     the number reaches the wire as a number. Declaring these `string` was
     inaccurate; coercing them instead would change the request body. */
  _interests: number[];
  /* `"yes" | "no" | ""`, not `string`: the select offers exactly the two
     (`healthConcernOptions`) and clearing it yields `""`. The endpoint
     validates `in:yes,no`, so a third value would be a 422 — and the submit
     maps `""` to `"no"` before sending. */
  health_concerns: "yes" | "no" | "";
  /** BE-95 — real name on the public profile; certificates always use it. */
  show_real_name: boolean;
  /** BE-96 — no email except OTP and account matters; the rest become notifications. */
  do_not_disturb: boolean;
  gender: number | "";
  /** Combined nationality/residency choice; split into API fields on submit. */
  nationality: string;
  /** BE-77 — "" | "true" | "false"; blank stays unanswered on the wire. */
  speaks_arabic: string;
  dob: string;
  civil_id: string;
  passport_number: string;
  emergency_contact_name: string;
  emergency_contact_phone: string;
  emergency_contact_country_code: string;
  emergency_contact_civil_id: string;
  emergency_contact_relationship: number | "";
  socialMedia: Array<{ platform: string; link: string }>;
}
