Ordering Selector & Asset Publishing

Overview

v3.4.1 restored the ordering portal's address selector to full parity and closed an asset-publishing gap in the production build pipeline.

Address Selector Restoration

The address_autocomplete_controller.js Stimulus controller was rewritten (~1,200 lines added) to switch from calling /api/address/insight on the local platform to calling dossier-api directly at /api/insights, making the ordering portal use dossier-api as its source of truth for address resolution.

A new MapshareGeocoderSuggestController provides a server-side proxy that forwards vicplan preset suggestions through dossier-api first, falling back to the local suggestion service on failure. The controller gained substantial new logic for:

• Title status resolution via TomSelect
• SPEAR milestone preview refresh
• SOC and predicted-title-date derivation from milestones
• Suggestion reordering by relevance
• A mapDossierInsightsToLegacyFormat() adapter that translates the dossier-api bundle into the flat format populateAddressFields() expects

Templates pass a dossier-api-url data attribute to the Stimulus controller, wired from a new DOSSIER_API_URL environment variable exposed as a Twig global.

Asset Publishing Fix

The production bootstrap script (bootstrap-prod.ts) was missing bun run assets steps for both app/ and ordering/. Without these, Symfony-managed assets (bundles like EasyAdmin, FOSCKEditor, etc.) were not published to public/bundles/ during production deploys, causing missing CSS/JS at runtime. Two new pipeline steps were added after each Webpack build to run assets:install.

Configuration

• ordering/.env - added environment configuration
• ordering/config/packages/twig.yaml - template path configuration
• ordering/config/services.yaml - service wiring for the new controller
• .gitignore - updated to track generated asset directories correctly

Files Touched

Changelog Reference

• fix: restore ordering address selector and asset publishing (#659)