Skip to content
This repository was archived by the owner on Feb 22, 2023. It is now read-only.

Conversation

@AsturaPhoenix
Copy link

@AsturaPhoenix AsturaPhoenix commented Jan 17, 2023

Saves tile bytes to blobs and uses img elements to decode and render. Does not implement opacity, perform caching, or serve placeholder images.

Issue: flutter/flutter#98596

Known issues:

Pre-launch Checklist

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • I read the Tree Hygiene wiki page, which explains my responsibilities.
  • I read and followed the relevant style guides and ran the auto-formatter. (Unlike the flutter/flutter repo, the flutter/plugins repo does use dart format.)
  • I signed the CLA.
  • The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
  • I listed at least one issue that this PR fixes in the description above.
  • I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or this PR is exempt from version changes.
  • I updated CHANGELOG.md to add a description of the change, following repository CHANGELOG style.
  • I updated/added relevant documentation (doc comments with ///).
  • I added new tests to check the change I am making, or this PR is test-exempt.
  • All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Saves tile bytes to blobs and uses `img` elements to decode and render. Does not
implement opacity, perform caching, or serve placeholder images.
Clears the tile cache for an overlay by re-setting the overlay in the map `MVCArray`.
No change in functionality or generated mocks; more concise.
Capture arguments to verified mock calls directly rather than using capture + expect. This also collapses the 'empty infoWindow does not create InfoWindow instance.' test into the previous test + a test of `google_maps_flutter_platform_interface`, so it can be removed without loss of coverage or functional specificity.
GoogleMapsController tests for tile overlays
GoogleMapsPlugin tests for tile overlays
Minor version bump for custom tile overlays.
Lock to 2013, and add omissions.
Add comment for new test image resource, and correct an adjacent typo.
This rule was removed, and this usage should be safe.
@AsturaPhoenix
Copy link
Author

@AsturaPhoenix
Copy link
Author

Locally when I try to run against flutter 2.10.5, I get

dart run ./script/tool/bin/flutter_plugin_tools.dart analyze --lib-only --skip-if-not-supporting-flutter-version="2.10.5" --skip-if-not-supporting-dart-version="2.16.2" --custom-analysis=script/configs/custom_analysis.yaml --packages google_maps_flutter_web
Resolving dependencies in C:\Users\imagi\Documents\projects\flutter\plugins\packages\google_maps_flutter\google_maps_flutter_web...
Because every version of flutter_test from sdk depends on collection 1.15.0 and google_maps_flutter_web depends on collection ^1.16.0, flutter_test from sdk is forbidden.
So, because google_maps_flutter_web depends on flutter_test from sdk, version solving failed.

Which isn't the kind of hang we're seeing on CI.

Not sure about next steps.

@AsturaPhoenix
Copy link
Author

AsturaPhoenix commented Jan 17, 2023

Oh, I think I get it. This is its way of telling me to bump something in pubspec.yaml huh?

environment:
  sdk: ">=2.12.0 <3.0.0"
  flutter: ">=2.10.0"

Or maybe I'll see if I can relax the collections dependency in a way that's compatible with both versions.

Updates pubspec.yaml environment version constraints to reflect dependency requirements:
* Dart 2.17.0 for mockito
* Flutter 3.0.0 for collection (upgraded in 2.13.0-..., but those don't seem to be releases)
We need to go back to the future. After upgrading environment constraints, the analyzer picks up cases where we should use super parameters.
img.src = src;
await img.decode();
img.hidden = false;
Url.revokeObjectUrl(src);
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We might want to put this in a finally. On the other hand, not revoking the blob URL in the case of a decoding failure may actually make debugging easier.

@stuartmorgan-g
Copy link
Contributor

Per discussion offline with @ditman, google_maps_flutter reviews have been on hold for now due to high-priority work on another plugin, but will be next on the queue. Thanks for being patient on the review here!

expect(capturedPolylines.first.polylineId.value, 'polyline-1');
});

testWidgets('empty infoWindow does not create InfoWindow instance.',
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Leaving a comment here because it wasn't obvious to me the second time I looked at it:

This test was removed because it became trivial once using Mockito verification; it essentially tests to make sure that Marker.infoWindow defaults to InfoWindow.noText. On the other hand, the argument could be made to keep it anyway (e.g. to construct the verification with an explicit infoWindow: InfoWindow.noText); let me know if you'd prefer that.

@stuartmorgan-g
Copy link
Contributor

We've just completed the migration of the plugin code to the flutter/packages repository, as described in https://flutter.dev/go/flutter-plugins-repo-migration, and this repository is now being archived. Unfortunately that means that all in-progress PRs here must be moved to flutter/packages.

Please see our instructions for an explanation of how to move your PR, and if you have any issues moving your PR please don't hesitate to reach out in the #hackers-ecosystem channel in Discord.

Our apologies that your PR was caught in this one-time transition. We're aware that it's disruptive in the short term, and appreciate your help in getting us to a better long-term state!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants