@autobusal/providers 1.37.10 → 1.37.11

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## 1.37.11
+
+### Added
+
+- Saved-passenger types and the account query, shared by the checkout chooser and the account manager so both read one shape.
+
 ## 1.37.10
 
 ### Added

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@autobusal/providers",
-  "version": "1.37.10",
+  "version": "1.37.11",
   "author": "Ferjolt Ozuni",
   "type": "module",
   "main": "index.ts"

package/types/persons.ts

@@ -14,4 +14,68 @@ export interface BillingData {
   bill_nipt: string
   comments: string
   terms: string
-}
+}
+/**
+ * A traveller this account has asked us to remember.
+ *
+ * Edited: Claude - Date: 2026-08-20
+ *
+ * Here rather than in either package that uses it, because BOTH do: the
+ * checkout chooser (@autobusal/routes-order) and the account manager
+ * (@autobusal/account-passengers) read the same rows from the same
+ * endpoints, and two copies of this shape would be free to disagree about
+ * the one field that matters most - which of them carries a passport number.
+ *
+ * THE LIST NEVER CARRIES THE NUMBER. `passport_masked` is the last few
+ * characters, enough to tell two of your own documents apart;
+ * `has_passport` is the yes/no. The raw value exists only on
+ * SavedPassengerRecord, which is what /get answers with - see obtapi's
+ * Account\PassengersController for why the split is there.
+ */
+export interface SavedPassenger {
+  id: number
+
+  first_name: string
+  last_name: string
+  /** d/m/Y, the format every date field in this app is typed in */
+  dob: string
+
+  /** what this person was last ticketed as - a record, never a price */
+  type: string | null
+  /** the fare band they fall into TODAY, derived from `dob` by the server */
+  age_type: 'adult' | 'child' | 'baby'
+
+  sex: number | null
+
+  passport_masked: string | null
+  has_passport: boolean
+
+  phone: string | null
+  whatsapp: string | null
+  telegram: string | null
+  email: string | null
+
+  /**
+   * What the journey being booked would still have to ask for - the option
+   * keys of routes_trip.passenger_fields (sex, passport, phone, whatsapp,
+   * telegram).
+   *
+   * ABSENT, not empty, when no journey was named: the account page asks for
+   * the list with no price ids and gets no `missing` at all, and reading
+   * that as "nothing missing" would be a promise about a route nobody has
+   * chosen yet. Hence optional, and hence every reader tests for an array
+   * rather than for length.
+   */
+  missing?: string[]
+}
+
+/** One traveller, passport included - the answer /get alone gives */
+export interface SavedPassengerRecord extends SavedPassenger {
+  passport: string | null
+}
+
+export interface SavedPassengersData {
+  data: SavedPassenger[]
+  /** how many one account may keep, so a UI can say so before refusing */
+  max: number
+}