The Places API googleMapsUri is a cid-style URL with no ftid, so the search/getPlaceDetails fixtures had stored a fabricated ftid. Switch them to real cid URLs and assert google_ftid is null — the precise query_place_id link still fixes the wrong-spot bug — and document the behaviour on googleFtidFromMapsUrl. - add a direct googleFtidFromMapsUrl test: extracts a real /place ftid, returns null for a cid URL, rejects malformed/hostile values - add placeGoogleMaps.test.ts covering the whole fallback chain (ftid -> place_id -> details URL -> coords) and the hostile-ftid rejection - PlaceInspector: use a freshly-fetched ftid when the place hasn't stored one |
||
|---|---|---|
| .. | ||
| db | ||
| mcp | ||
| middleware | ||
| nest | ||
| services | ||
| systemNotices | ||
| utils | ||
| idempotency-cleanup.test.ts | ||
| scheduler.test.ts | ||
| shared-contract.test.ts | ||