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
35 lines
2.0 KiB
JavaScript
35 lines
2.0 KiB
JavaScript
import { VALID_PUNCTUATION } from '../constants.js'
|
|
|
|
// Removes brackets and replaces dashes with spaces.
|
|
//
|
|
// E.g. "(999) 111-22-33" -> "999 111 22 33"
|
|
//
|
|
// For some reason Google's metadata contains `<intlFormat/>`s with brackets and dashes.
|
|
// Meanwhile, there's no single opinion about using punctuation in international phone numbers.
|
|
//
|
|
// For example, Google's `<intlFormat/>` for USA is `+1 213-373-4253`.
|
|
// And here's a quote from WikiPedia's "North American Numbering Plan" page:
|
|
// https://en.wikipedia.org/wiki/North_American_Numbering_Plan
|
|
//
|
|
// "The country calling code for all countries participating in the NANP is 1.
|
|
// In international format, an NANP number should be listed as +1 301 555 01 00,
|
|
// where 301 is an area code (Maryland)."
|
|
//
|
|
// I personally prefer the international format without any punctuation.
|
|
// For example, brackets are remnants of the old age, meaning that the
|
|
// phone number part in brackets (so called "area code") can be omitted
|
|
// if dialing within the same "area".
|
|
// And hyphens were clearly introduced for splitting local numbers into memorizable groups.
|
|
// For example, remembering "5553535" is difficult but "555-35-35" is much simpler.
|
|
// Imagine a man taking a bus from home to work and seeing an ad with a phone number.
|
|
// He has a couple of seconds to memorize that number until it passes by.
|
|
// If it were spaces instead of hyphens the man wouldn't necessarily get it,
|
|
// but with hyphens instead of spaces the grouping is more explicit.
|
|
// I personally think that hyphens introduce visual clutter,
|
|
// so I prefer replacing them with spaces in international numbers.
|
|
// In the modern age all output is done on displays where spaces are clearly distinguishable
|
|
// so hyphens can be safely replaced with spaces without losing any legibility.
|
|
//
|
|
export default function applyInternationalSeparatorStyle(formattedNumber) {
|
|
return formattedNumber.replace(new RegExp(`[${VALID_PUNCTUATION}]+`, 'g'), ' ').trim()
|
|
} |