fix(map): keep URL/UI in sync on tap failure; handle antimeridian in padBounds

- selectListingById no longer sets the error sentinel when the fetch fails.
  Tap-driven fetches happen before the URL is pushed, so the drawer would
  either stay closed (swallowing the error) or desync UI and URL while
  pointing at the previous listing. The optimistic pin id is reverted and
  `selectedListing` is left untouched, so UI and URL stay consistent.
- padBounds now wraps longitudes into [-180, 180] and splits the envelope
  into two when the padded viewport crosses the antimeridian. Callers
  iterate all returned boxes.
- useListingsInView fetches all returned boxes in parallel and merges
  responses, deduping by id.

Made-with: Cursor

Author: dnywh

src/features/map/hooks/useListingsInView.ts

@@ -65,24 +65,35 @@ export function useListingsInView(): UseListingsInViewResult {
   const inFlightCountRef = useRef(0);
 
   const runFetch = useCallback(async (bounds: LngLatBounds) => {
-    const padded = padBounds(bounds, VIEWPORT_PAD_FACTOR);
+    // `padBounds` returns 1 box normally, or 2 when the viewport crosses the
+    // antimeridian. We fetch each and merge, deduping by id.
+    const paddedBoxes = padBounds(bounds, VIEWPORT_PAD_FACTOR);
 
     const requestId = ++requestIdRef.current;
     inFlightCountRef.current += 1;
     setIsFetching(true);
 
     try {
-      const data = await fetchListingsInView(
-        padded.south,
-        padded.west,
-        padded.north,
-        padded.east
+      const responses = await Promise.all(
+        paddedBoxes.map((box) =>
+          fetchListingsInView(box.south, box.west, box.north, box.east)
+        )
       );
 
       // Ignore stale responses — a newer request has already superseded this one.
       if (requestId !== requestIdRef.current) return;
 
-      setListings((data ?? []) as ListingMarker[]);
+      const seen = new Set<number>();
+      const merged: ListingMarker[] = [];
+      for (const response of responses) {
+        for (const marker of (response ?? []) as ListingMarker[]) {
+          if (seen.has(marker.id)) continue;
+          seen.add(marker.id);
+          merged.push(marker);
+        }
+      }
+
+      setListings(merged);
     } catch (error) {
       if (requestId !== requestIdRef.current) return;
       console.error("Error fetching listings in view:", error);

src/features/map/hooks/useMapListingUrl.ts

@@ -187,10 +187,12 @@ export function useMapListingUrl({
         if (token !== requestTokenRef.current) return;
 
         if (error || !data) {
-          setSelectedListing({
-            error: true,
-            message: t("Listings.edit.notFound"),
-          });
+          // Tap-driven fetches happen before the URL is pushed, so surfacing
+          // an error sentinel here would either be invisible (no listing in
+          // URL → drawer stays closed) or desync the UI from the URL (still
+          // pointing at the previous listing). Revert the optimistic pin and
+          // leave `selectedListing` alone instead.
+          console.warn("Failed to select listing by id:", error);
           setOptimisticListingId(null);
           return;
         }
@@ -208,14 +210,10 @@ export function useMapListingUrl({
       } catch (err) {
         if (token !== requestTokenRef.current) return;
         console.warn("Failed to select listing by id:", err);
-        setSelectedListing({
-          error: true,
-          message: t("Listings.edit.notFound"),
-        });
         setOptimisticListingId(null);
       }
     },
-    [router, supabase, t, tableName]
+    [router, supabase, tableName]
   );
 
   const closeListing = useCallback(() => {

src/features/map/lib/mapUtils.ts

@@ -79,10 +79,23 @@ export function hasValidCoordinates(
   );
 }
 
+// Wrap a longitude into the canonical [-180, 180] range. MapLibre reports
+// bounds as "unwrapped" coordinates (values outside the canonical range when
+// the user has panned across the antimeridian), but the `listings_in_view`
+// RPC feeds them into PostGIS' `st_makeenvelope`, which expects canonical
+// longitudes.
+function wrapLongitude(lng: number): number {
+  return ((((lng + 180) % 360) + 360) % 360) - 180;
+}
+
 // Expand a viewport bbox by a fraction (e.g. 0.3 => 30% larger in each
 // direction). This lets us fetch a slightly padded area so that small pans
 // reuse already-loaded pins without hitting the network again.
-export function padBounds(bounds: LngLatBounds, factor = 0.3): BoundingBox {
+//
+// Returns 1 or 2 boxes. Two are returned when the padded viewport crosses
+// the antimeridian (e.g. Fiji, NZ → Alaska), so the caller can fetch both
+// halves and merge the results.
+export function padBounds(bounds: LngLatBounds, factor = 0.3): BoundingBox[] {
   const sw = bounds.getSouthWest();
   const ne = bounds.getNorthEast();
 
@@ -92,12 +105,27 @@ export function padBounds(bounds: LngLatBounds, factor = 0.3): BoundingBox {
   const latPad = latSpan * factor;
   const lngPad = lngSpan * factor;
 
-  return {
-    south: Math.max(-90, sw.lat - latPad),
-    north: Math.min(90, ne.lat + latPad),
-    west: sw.lng - lngPad,
-    east: ne.lng + lngPad,
-  };
+  const south = Math.max(-90, sw.lat - latPad);
+  const north = Math.min(90, ne.lat + latPad);
+
+  // If the padded viewport already covers the whole globe, just request the
+  // whole world (avoids degenerate envelopes in PostGIS).
+  if (lngSpan + 2 * lngPad >= 360) {
+    return [{ south, north, west: -180, east: 180 }];
+  }
+
+  const west = wrapLongitude(sw.lng - lngPad);
+  const east = wrapLongitude(ne.lng + lngPad);
+
+  if (west <= east) {
+    return [{ south, north, west, east }];
+  }
+
+  // Crosses the antimeridian — split into two valid envelopes.
+  return [
+    { south, north, west, east: 180 },
+    { south, north, west: -180, east },
+  ];
 }
 
 export function isCoordinateInBounds(