PhongPham
c65cc97a33
✨ MAJOR FEATURES: • Auto-zoom intelligence với smart bounds fitting • Enhanced 3D GPS markers với pulsing effects • Professional route display với 6-layer rendering • Status-based parking icons với availability indicators • Production-ready build optimizations 🗺️ AUTO-ZOOM FEATURES: • Smart bounds fitting cho GPS + selected parking • Adaptive padding (50px) cho visual balance • Max zoom control (level 16) để tránh quá gần • Dynamic centering khi không có selection 🎨 ENHANCED VISUALS: • 3D GPS marker với multi-layer pulse effects • Advanced parking icons với status colors • Selection highlighting với animation • Dimming system cho non-selected items 🛣️ ROUTE SYSTEM: • OpenRouteService API integration • Multi-layer route rendering (glow, shadow, main, animated) • Real-time distance & duration calculation • Visual route info trong popup 📱 PRODUCTION READY: • SSR safe với dynamic imports • Build errors resolved • Global deployment via Vercel • Optimized performance 🌍 DEPLOYMENT: • Vercel: https://whatever-ctk2auuxr-phong12hexdockworks-projects.vercel.app • Bundle size: 22.8 kB optimized • Global CDN distribution • HTTPS enabled 💾 VERSION CONTROL: • MapView-v2.0.tsx backup created • MAPVIEW_VERSIONS.md documentation • Full version history tracking
31 lines
1.8 KiB
TypeScript
31 lines
1.8 KiB
TypeScript
import type { FlightRouterState } from '../../../server/app-render/types';
|
|
import type { CacheNode } from '../../../shared/lib/app-router-context.shared-runtime';
|
|
import type { AppRouterState } from './router-reducer-types';
|
|
interface RefreshInactiveParallelSegments {
|
|
state: AppRouterState;
|
|
updatedTree: FlightRouterState;
|
|
updatedCache: CacheNode;
|
|
includeNextUrl: boolean;
|
|
canonicalUrl: string;
|
|
}
|
|
/**
|
|
* Refreshes inactive segments that are still in the current FlightRouterState.
|
|
* A segment is considered "inactive" when the server response indicates it didn't match to a page component.
|
|
* This happens during a soft-navigation, where the server will want to patch in the segment
|
|
* with the "default" component, but we explicitly ignore the server in this case
|
|
* and keep the existing state for that segment. New data for inactive segments are inherently
|
|
* not part of the server response when we patch the tree, because they were associated with a response
|
|
* from an earlier navigation/request. For each segment, once it becomes "active", we encode the URL that provided
|
|
* the data for it. This function traverses parallel routes looking for these markers so that it can re-fetch
|
|
* and patch the new data into the tree.
|
|
*/
|
|
export declare function refreshInactiveParallelSegments(options: RefreshInactiveParallelSegments): Promise<void>;
|
|
/**
|
|
* Walks the current parallel segments to determine if they are "active".
|
|
* An active parallel route will have a `__PAGE__` segment in the FlightRouterState.
|
|
* As opposed to a `__DEFAULT__` segment, which means there was no match for that parallel route.
|
|
* We add a special marker here so that we know how to refresh its data when the router is revalidated.
|
|
*/
|
|
export declare function addRefreshMarkerToActiveParallelSegments(tree: FlightRouterState, path: string): void;
|
|
export {};
|