Admin side only.
Problem
The ride-detail Edit modal uses plain free-text UInput fields for pickup/dropoff (app/pages/rides/[id].vue:563-569), while the create flow now uses the DB-search AddressField (search existing saved addresses / "enter a new address", which reuses Address rows and dedupes on matchKey). Editing an address bypasses all of that.
Proposal
- Replace the two text inputs with
AddressField (v-model a RideAddressForm { street, city, state, zip }), mapping to pickupDisplay/dropoffDisplay for the PUT.
- Server already upserts addresses on
matchKey (R-101), so no duplicate rows.
Acceptance criteria
- Editing an address uses the same search-existing / enter-new UX as create.
- Save still works via
PUT /api/put/rides/[id].
Notes
Current PUT takes pickupDisplay/dropoffDisplay strings — reconcile the structured form ↔ display string on save.
Admin side only.
Problem
The ride-detail Edit modal uses plain free-text
UInputfields for pickup/dropoff (app/pages/rides/[id].vue:563-569), while the create flow now uses the DB-searchAddressField(search existing saved addresses / "enter a new address", which reusesAddressrows and dedupes onmatchKey). Editing an address bypasses all of that.Proposal
AddressField(v-model aRideAddressForm { street, city, state, zip }), mapping topickupDisplay/dropoffDisplayfor thePUT.matchKey(R-101), so no duplicate rows.Acceptance criteria
PUT /api/put/rides/[id].Notes
Current
PUTtakespickupDisplay/dropoffDisplaystrings — reconcile the structured form ↔ display string on save.