Ordering Portal LOT Address Canonicalisation
Picking a "Lot on Street" suggestion on the ordering portal now rewrites the input to canonical LOT N (streetNo) STREET SUBURB shape instead of the raw ArcGIS label
Overview
On the ordering portal's Create New Project form, picking an autocomplete suggestion such as Lot 143 RAMPART STREET DONNYBROOK (143\PS908985 - 8) left the input on the raw ArcGIS label. The expected behaviour - already shipped on the customer/admin platform back in the 3.7 train - was to rewrite the value to the canonical LOT 143 (8) RAMPART STREET DONNYBROOK shape on selection. The ordering portal had silently missed the original port (Trello 1762).
Behaviour after the fix
| Action | Before | After |
|---|---|---|
Type lot 143 rampart, pick suggestion | Input keeps Lot 143 RAMPART STREET DONNYBROOK (143\PS908985 - 8) | Input flips immediately to LOT 143 (8) RAMPART STREET DONNYBROOK |
| Downstream SPI / LGA auto-population | Triggered off non-canonical value | Triggered off canonical value, identical to customer/admin |
The canonicalisation runs against display_address, lot_address, and ezi_address payloads from the autocomplete API, and an input event is dispatched alongside the existing change event so reactive Stimulus listeners pick the change up immediately rather than only on blur.
Verification
Reproduced end-to-end against https://preprod-ordering.ftsonline.com.au/project/select and https://ordering.ftsonline.com.au/project/select using the Donnybrook lot. The autocomplete suggestion is rewritten on selection, SPI and LGA fields auto-populate from the canonical value, and the project save flow proceeds without further intervention.