flutter_polyline_points 3.1.0

flutter_polyline_points: ^3.1.0 copied to clipboard

• ENHANCED: Added validation for bicycling and walking travel modes to ensure they use RoutingPreference.unspecified as required by Google Routes API.
  • Special thanks to @enricava for the contribution.
• Fixed: Decoding issue on web.
• Fixed: Decoding intermediate locations issue.
  • Thanks to @razosx

• NEW: Add support for custom headers in Routes API requests.

🚀 Major Refactor - Simplified and Unified API #

Unified PolylinePoints Class

• BREAKING: Simplified API with single PolylinePoints class for both APIs
• BREAKING: Constructor now requires apiKey parameter
• NEW: Factory constructors: PolylinePoints.legacy(), PolylinePoints.enhanced(), PolylinePoints.custom()
• ENHANCED: Unified interface supporting both Directions API and Routes API

Enhanced Routes API Integration

• NEW: RoutesApiRequest model with comprehensive parameter support
• NEW: RoutesApiResponse model with improved type safety
• NEW: Custom body parameters support for advanced use cases
• NEW: Field mask support for response optimization
• NEW: Two-wheeler routing mode support

Improved Request/Response Models

• NEW: RouteModifiers for enhanced route customization
• NEW: Timing preferences with departure/arrival time support
• NEW: Convenience getters: durationMinutes, staticDurationMinutes, distanceKm
• ENHANCED: Better type safety and null handling
• ENHANCED: Polyline decoding integration with automatic point conversion

Developer Experience

• NEW: Comprehensive test coverage for reliability
• NEW: convertToLegacyResult() method for API compatibility
• NEW: Enhanced error handling and validation
• IMPROVED: Code documentation and examples
• IMPROVED: Better parameter validation and error messages

🔧 Technical Improvements #

• ENHANCED: Network utilities with better error handling
• ENHANCED: Polyline decoder with robust error handling
• NEW: Static decodePolyline method for utility usage
• IMPROVED: JSON serialization and deserialization
• IMPROVED: Memory efficiency and performance

🛠️ Breaking Changes #

• BREAKING: PolylinePoints constructor now requires apiKey parameter
• BREAKING: Removed googleApiKey parameter from method calls
• BREAKING: Simplified class structure (removed separate V2 classes)
• MIGRATION: Update constructor calls and remove googleApiKey from method parameters

📚 Migration Support #

• MAINTAINED: Full backward compatibility for legacy Directions API
• NEW: Clear migration path from v2.x to v3.0
• NEW: Updated documentation with migration examples
• NEW: Factory constructors for different use cases

• Breaking change, getRouteBetweenCoordinates now requires a PolylineRequest object
• Updated http package
• Bug fixes and general improvements Special thanks to these contributors:
• @tetrix
• @fadimanakilci
• @anixsam

Updated dependencies and added some new functionalities such as:

• Fetching alternative routes
• Optimised algorithm for web Special thanks to this contibutors for landing such huge PRs:
• @nnadir35
• @shkvoretz

Released a null safety version

updated http package

updating http dependency to ^0.13.0

Fixed issues with waypoint

Fixed a bug with adding waypoint to request thanks to EnzoSeason

FIxed issues with incorrect key being passed as travelmode Changed waypoint documentation

Breaking change, the response object has been refined to a more suitable object that contains the status of the api and the error message.

Add travel mode, thanks to @tuxbook Fixed unhandled error exception.

update readme.

initial release.