feat: Enhance Routes API integration and fix decoding issues#126
Merged
Conversation
This commit introduces several improvements and bug fixes related to the Google Routes API integration and polyline decoding. Key changes: - **ENHANCED**: Added validation for `bicycling` and `walking` travel modes to ensure they use `RoutingPreference.unspecified` as required by the Google Routes API. This prevents potential API errors and ensures correct route calculations. - **FIXED**: Resolved a polyline decoding issue that primarily affected web platforms. The decoding logic has been updated to correctly handle `BigInt` operations, ensuring accurate coordinate parsing. - **FIXED**: Corrected an issue with decoding intermediate locations in API responses. - **CHORE**: Updated the `http` package dependency to version `^1.5.0`. - **CHORE**: Set `publish_to: none` in the example app's `pubspec.yaml` to prevent accidental publishing. - **TEST**: Added a GitHub Actions workflow for automated testing, linting, formatting, and dry-run publishing on pull requests. - **TEST**: Introduced new unit tests for network provider functionality, specifically focusing on header handling in `RoutesApiRequest`. - **TEST**: Updated integration tests to reflect the routing preference change for walking mode. - **TEST**: Removed old `polyline_points_test.dart` and `widget_test.dart` from the example app as they were outdated or redundant. - **DOCS**: Updated CHANGELOG.md with details of these changes. - Incremented package version to 3.1.0.
️✅ There are no secrets present in this pull request anymore.If these secrets were true positive and are still valid, we highly recommend you to revoke them. 🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request. |
This commit focuses on improving code style and consistency across the project by applying automated code formatting. Additionally, some redundant newlines and comments have been removed to enhance readability. Key changes: - Applied Dart formatter to various files including tests, library code, and example app. - Removed unnecessary empty lines in multiple files. - Removed a redundant test file `test/flutter_polyline_points_test.dart` from `.gitignore` as it was already covered by other tests or was a duplicate. - Minor cleanup of comments and spacing in classes like `PointLatLng`, `PolylineWayPoint`, and API model classes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This commit introduces several improvements and bug fixes related to the Google Routes API integration and polyline decoding.
Key changes:
bicyclingandwalkingtravel modes to ensure they useRoutingPreference.unspecifiedas required by the Google Routes API. This prevents potential API errors and ensures correct route calculations.BigIntoperations, ensuring accurate coordinate parsing.httppackage dependency to version^1.5.0.publish_to: nonein the example app'spubspec.yamlto prevent accidental publishing.RoutesApiRequest.polyline_points_test.dartandwidget_test.dartfrom the example app as they were outdated or redundant.