Maurice 0b2780ead2 test: make the Google Maps ftid path honest + cover the URL helper ... 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		2026-06-27 20:14:52 +02:00
..
e2e	v3.1.1 bug fixes (#1228)	2026-06-18 20:13:30 +02:00
fixtures	feat(import): selective GPX/KML element import and performance improvements	2026-04-18 01:28:37 +02:00
helpers	Release 3.1.0 (#1185)	2026-06-16 22:22:45 +02:00
integration	fix(atlas): gzip-compress responses so large country GeoJSON loads behind reverse proxies (#1262)	2026-06-23 21:23:39 +02:00
unit	test: make the Google Maps ftid path honest + cover the URL helper	2026-06-27 20:14:52 +02:00
websocket	Release 3.1.0 (#1185)	2026-06-16 22:22:45 +02:00
setup.ts	Add comprehensive backend test suite (#339)	2026-04-03 13:17:53 +02:00