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

[google_maps_flutter_platform_interface] Add dispose method. #2908

Merged
merged 1 commit into from
Aug 10, 2020

Conversation

ditman
Copy link
Member

@ditman ditman commented Aug 7, 2020

Description

The current version of the plugin does not have the ability to dispose of the resources that it grabs natively (I suppose the native side is able to clean itself up effectively).

The web implementation is not able to do so, and it needs a dispose method to dispose of the resources it grabs.

This PR adds a dispose method to the platform interface package of google_maps_flutter, and a noop implementation for its MethodChannel implementation.

The new method will be called on dispose of the current GoogleMap widget, as seen here: #2909

Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
  • All existing and new tests are passing.
  • I updated/added relevant documentation (doc comments with ///).
  • The analyzer (flutter analyze) does not report any problems on my PR.
  • I read and followed the Flutter Style Guide.
  • The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
  • I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
  • I updated CHANGELOG.md to add a description of the change.
  • I signed the CLA.
  • I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

  • No, this is not a breaking change.

Copy link
Contributor

@cyanglaz cyanglaz left a comment

Choose a reason for hiding this comment

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

Who is going to be the caller? Each plugin decides when to call?

@cyanglaz
Copy link
Contributor

cyanglaz commented Aug 7, 2020

Just saw #2909. will take another look.

@ditman
Copy link
Member Author

ditman commented Aug 7, 2020

@cyanglaz This will be called on dispose of the GoogleMap widget.

Copy link
Contributor

@cyanglaz cyanglaz left a comment

Choose a reason for hiding this comment

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

LGTM

@ditman ditman merged commit 740481e into flutter:master Aug 10, 2020
jarrodcolburn pushed a commit to jarrodcolburn/plugins that referenced this pull request Aug 20, 2020
…#2908)

This method gives the plugin writers a chance to release the resources that they've acquired throughout the operation of the plugin (think of it as an "inverse" of the "init" method).
@ditman ditman deleted the gmaps-add-dispose branch August 25, 2020 22:04
jorgefspereira pushed a commit to jorgefspereira/plugins_flutter that referenced this pull request Oct 10, 2020
…#2908)

This method gives the plugin writers a chance to release the resources that they've acquired throughout the operation of the plugin (think of it as an "inverse" of the "init" method).
FlutterSu pushed a commit to FlutterSu/flutter-plugins that referenced this pull request Nov 20, 2020
…#2908)

This method gives the plugin writers a chance to release the resources that they've acquired throughout the operation of the plugin (think of it as an "inverse" of the "init" method).
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants