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

[google_maps_flutter] Default Android to Hybrid Composition #6334

Merged
merged 4 commits into from
Sep 1, 2022

Conversation

stuartmorgan
Copy link
Contributor

Updates Android implementation to use Hybrid Composition by default.

It's debatable whether this is a breaking change (since code calling this API will still compile, and explicitly setting it will still do the same thing it used it, it just has a different default). I'm choosing to treat it as non-breaking given than the primary expected effect is working around a serious regression caused by the display mode change in Flutter 3.0.

This will make the documentation in the app-facing package incorrect about the default behavior, but I'll do a separate PR at the same time (combining them would fail the federation safety check even though it's technically okay in this case) to update those docs. Technically someone could have the old app-facing package with the old docs, but the new implementation package with the new default, and see a mismatch between docs and default, but that's an small edge case, and won't actually break anything, so isn't worth making it a breaking change just for that.

Mostly resolves flutter/flutter#103686 until we can fix updates under TLHC.
Mostly resolves flutter/flutter#39797, although we should ensure that's fixed under TLHC (it may already be).
Fixes flutter/flutter#93335

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.

Copy link
Contributor

@bparrishMines bparrishMines left a comment

Choose a reason for hiding this comment

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

LGTM

Comment on lines +17 to +19
// #enddocregion DisplayMode
runApp(const MaterialApp());
// #docregion DisplayMode
Copy link
Contributor

@bparrishMines bparrishMines Sep 1, 2022

Choose a reason for hiding this comment

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

I'm assuming this just cuts out the runApp line from the doc region? I didn't know you could do that. Took me a minute to understand it.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yep, code-excerpts lets you make non-contiguous pulls, and adds (by default) a // ... (or whatever makes sense for the language) in the generated output.

@stuartmorgan stuartmorgan added the autosubmit Merge PR when tree becomes green via auto submit App label Sep 1, 2022
@auto-submit auto-submit bot merged commit c570327 into flutter:main Sep 1, 2022
stuartmorgan added a commit to stuartmorgan/plugins that referenced this pull request Sep 1, 2022
Some integration tests behave slightly differently on Android when using
Hybrid Composition, and need to wait for a change to become true rather
than it being immediately true.

This replicates the changes from `google_maps_flutter_android` to the
app-facing copy of those integration tests.

Fixes tree breakage from publishing
flutter#6334
stuartmorgan added a commit that referenced this pull request Sep 1, 2022
Some integration tests behave slightly differently on Android when using
Hybrid Composition, and need to wait for a change to become true rather
than it being immediately true.

This replicates the changes from `google_maps_flutter_android` to the
app-facing copy of those integration tests.

Fixes tree breakage from publishing
#6334
adam-harwood pushed a commit to adam-harwood/flutter_plugins that referenced this pull request Nov 3, 2022
adam-harwood pushed a commit to adam-harwood/flutter_plugins that referenced this pull request Nov 3, 2022
Some integration tests behave slightly differently on Android when using
Hybrid Composition, and need to wait for a change to become true rather
than it being immediately true.

This replicates the changes from `google_maps_flutter_android` to the
app-facing copy of those integration tests.

Fixes tree breakage from publishing
flutter#6334
curt-weber pushed a commit to KWRI/google_maps_flutter that referenced this pull request Nov 3, 2022
Some integration tests behave slightly differently on Android when using
Hybrid Composition, and need to wait for a change to become true rather
than it being immediately true.

This replicates the changes from `google_maps_flutter_android` to the
app-facing copy of those integration tests.

Fixes tree breakage from publishing
flutter/plugins#6334
mauricioluz pushed a commit to mauricioluz/plugins that referenced this pull request Jan 26, 2023
mauricioluz pushed a commit to mauricioluz/plugins that referenced this pull request Jan 26, 2023
Some integration tests behave slightly differently on Android when using
Hybrid Composition, and need to wait for a change to become true rather
than it being immediately true.

This replicates the changes from `google_maps_flutter_android` to the
app-facing copy of those integration tests.

Fixes tree breakage from publishing
flutter#6334
engine-flutter-autoroll pushed a commit to engine-flutter-autoroll/packages that referenced this pull request Feb 22, 2023
Some integration tests behave slightly differently on Android when using
Hybrid Composition, and need to wait for a change to become true rather
than it being immediately true.

This replicates the changes from `google_maps_flutter_android` to the
app-facing copy of those integration tests.

Fixes tree breakage from publishing
flutter/plugins#6334
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
autosubmit Merge PR when tree becomes green via auto submit App p: google_maps_flutter platform-android
Projects
None yet
2 participants