Repository navigation
release: v0.6.74 - #410
Merged
Merged
release: v0.6.74#410
Conversation
The internal geocoder/query and geocoder/reverse endpoints used the geocoder-laravel facade, whose Google provider is built from config/geocoder.php when the config loads, before the API key from the settings table is set. Its Chain provider swallowed the resulting failure, so both endpoints returned [] while places/lookup, which goes through Geocoding, resolved the same address. Route both lookups through Geocoding::geocoder() so they share the settings-backed API key, region and locale. Fixes fleetbase/fleetbase#723
GeocoderController no longer resolves the geocoder-laravel facade, so
the seam test's app('geocoder') stand-in was never consulted and the
unbound fleetops geocoder tried a live Google request.
Place, PlaceSearch and the v1 Place and Driver controllers still called the geocoder-laravel facade. Its Google provider is built from config/geocoder.php when the config loads, before the settings-table API key is set, and its Chain provider swallows the failure, so these lookups silently returned no results (the same bug #408 fixed for the internal geocoder endpoints). They now go through Geocoding::geocoder(). Geocoding::lookupAddress() and lookupCoordinates() return the raw address results; a failed lookup still resolves to an empty collection, so place creation keeps its raw-address fallback, but the failure is now logged instead of hidden. The driver tracking endpoint keeps calling the geocoder directly so its failures still reach Sentry. config/geocoder.php now passes the region where GoogleMaps expects it (it passed the locale) and uses the default cache store instead of a 'geocode' store that does not exist. It only matters for code outside fleetops that still uses the facade. Tests bind 'fleetops.geocoder' stand-ins instead of app('geocoder'). Refs fleetbase/fleetbase#723
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #410 +/- ##
===========================================
Coverage 100.00% 100.00%
- Complexity 13591 13596 +5
===========================================
Files 634 634
Lines 49331 49342 +11
===========================================
+ Hits 49331 49342 +11
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
With every test injecting fleetops.geocoder, nothing built the live Google geocoder or reached Geocoding::query()'s rethrow, the import raw-address fallback, or PlaceSearch's outer guard.
…figured-geocoder fix: resolve geocoder endpoints through the configured fleetops geocoder
…e-configured-geocoder fix: route every geocoder lookup through the settings-backed geocoder
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release v0.6.74. Merging this PR into
maintagsv0.6.74through the release workflow.Included
#408, #409. These fix PRs target this branch; merge them here first, #408 before #409 (#409 is stacked on #408's commit).
Fixes fleetbase/fleetbase#723: the geocoder endpoints and every other geocoding path now use the Google Maps API key from settings. No migrations are needed.
The version files and
RELEASE.mdalready name v0.6.74. UpdateRELEASE.mdif anything else lands on this branch.