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
1.4 KiB
Markdown
35 lines
1.4 KiB
Markdown
# Change Log
|
|
All notable changes to this project will be documented in this file.
|
|
|
|
## [3.0.0]
|
|
### Changed
|
|
- **BREAKING**: `jwt.verify` now requires an `algorithm` parameter, and
|
|
`jws.createVerify` requires an `algorithm` option. The `"alg"` field
|
|
signature headers is ignored. This mitigates a critical security flaw
|
|
in the library which would allow an attacker to generate signatures with
|
|
arbitrary contents that would be accepted by `jwt.verify`. See
|
|
https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/
|
|
for details.
|
|
|
|
## [2.0.0] - 2015-01-30
|
|
### Changed
|
|
- **BREAKING**: Default payload encoding changed from `binary` to
|
|
`utf8`. `utf8` is a is a more sensible default than `binary` because
|
|
many payloads, as far as I can tell, will contain user-facing
|
|
strings that could be in any language. (<code>[6b6de48]</code>)
|
|
|
|
- Code reorganization, thanks [@fearphage]! (<code>[7880050]</code>)
|
|
|
|
### Added
|
|
- Option in all relevant methods for `encoding`. For those few users
|
|
that might be depending on a `binary` encoding of the messages, this
|
|
is for them. (<code>[6b6de48]</code>)
|
|
|
|
[unreleased]: https://github.com/brianloveswords/node-jws/compare/v2.0.0...HEAD
|
|
[2.0.0]: https://github.com/brianloveswords/node-jws/compare/v1.0.1...v2.0.0
|
|
|
|
[7880050]: https://github.com/brianloveswords/node-jws/commit/7880050
|
|
[6b6de48]: https://github.com/brianloveswords/node-jws/commit/6b6de48
|
|
|
|
[@fearphage]: https://github.com/fearphage
|