-
Notifications
You must be signed in to change notification settings - Fork 3.6k
[google_maps_flutter] Migrate Android heatmaps to Pigeon #10758
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[google_maps_flutter] Migrate Android heatmaps to Pigeon #10758
Conversation
Replaces the legacy JSON serialization of heatmaps with fully typed Pigeon data. Final Android portion of flutter/flutter#117907
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request successfully migrates the Android implementation of heatmaps from a JSON-based serialization to a type-safe approach using Pigeon. The changes are well-executed, replacing manual serialization and deserialization with generated, typed data classes for heatmaps, gradients, and weighted points. This significantly improves code quality, readability, and maintainability by leveraging the type system to prevent runtime errors. The related controllers, data conversion logic, and tests have been updated accordingly, and the overall implementation is clean and robust. No issues were found during the review.
flutter/packages@ce3afa4...c1b1183 2026-01-16 [email protected] Manual roll Flutter from b45a73b to 48c2475 (3 revisions) (flutter/packages#10814) 2026-01-16 [email protected] Manual roll Flutter from b45a73b to 5a2067b (4 revisions) (flutter/packages#10810) 2026-01-15 [email protected] [url_launcher] fix: tab traversal on web (flutter/packages#10020) 2026-01-15 [email protected] [google_maps_flutter] Migrate Android heatmaps to Pigeon (flutter/packages#10758) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/flutter-packages-flutter-autoroll Please CC [email protected] on the revert to ensure that a human is aware of the problem. To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
…r#181077) flutter/packages@ce3afa4...c1b1183 2026-01-16 [email protected] Manual roll Flutter from b45a73b to 48c2475 (3 revisions) (flutter/packages#10814) 2026-01-16 [email protected] Manual roll Flutter from b45a73b to 5a2067b (4 revisions) (flutter/packages#10810) 2026-01-15 [email protected] [url_launcher] fix: tab traversal on web (flutter/packages#10020) 2026-01-15 [email protected] [google_maps_flutter] Migrate Android heatmaps to Pigeon (flutter/packages#10758) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/flutter-packages-flutter-autoroll Please CC [email protected] on the revert to ensure that a human is aware of the problem. To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Replaces the legacy JSON serialization of heatmaps with fully typed Pigeon data.
Final Android portion of flutter/flutter#117907
Pre-Review Checklist
[shared_preferences]pubspec.yamlwith an appropriate new version according to the pub versioning philosophy, or I have commented below to indicate which version change exemption this PR falls under1.CHANGELOG.mdto add a description of the change, following repository CHANGELOG style, or I have commented below to indicate which CHANGELOG exemption this PR falls under1.///).Footnotes
Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩2 ↩3