[google_maps_flutter] Add support for mapType, fullscreen, and Street View controls on web

[puneetkukreja98]

This PR adds support for mapTypeControlEnabled, fullscreenControlEnabled, and streetViewControlEnabled on Flutter web.

Previously, these options were not exposed through the GoogleMap widget and were internally defaulted to false in MapConfiguration.

This change propagates these parameters through google_maps_flutter, google_maps_flutter_platform_interface, and google_maps_flutter_web, allowing developers to explicitly enable or disable these controls.

To preserve backward compatibility, the existing behavior is maintained by defaulting these options to false when they are not provided by the user.

I created a sample app and tested the changes using dependency_overrides. Attaching a video for reference.

google_maps_flutter_rec.mov

Fixes flutter/flutter#104111.

Pre-Review Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the AI contribution guidelines and understand my responsibilities, or I am not using AI tools.
• I read the Tree Hygiene page, which explains my responsibilities.
• I read and followed the relevant style guides and ran the auto-formatter.
• I signed the CLA.
• The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
• I linked to at least one issue that this PR fixes in the description above.
• I followed the version and CHANGELOG instructions, using semantic versioning and the repository CHANGELOG style, or I have commented below to indicate which documented exception this PR falls under¹.
• I updated/added any relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or I have commented below to indicate which test exemption this PR falls under¹.
• All existing and new tests are passing.

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

Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the gemini-code-assist bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

Footnotes

1. Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩²

[gemini-code-assist]

Code Review

This pull request adds support for mapTypeControlEnabled, fullscreenControlEnabled, and streetViewControlEnabled on the web platform across the google_maps_flutter, google_maps_flutter_platform_interface, and google_maps_flutter_web packages, along with corresponding unit and integration tests. Feedback from the reviewer highlights the need to update the dependency constraints for google_maps_flutter_platform_interface in the pubspec files of both google_maps_flutter and google_maps_flutter_web to prevent potential compilation failures.

[gemini-code-assist]

Since this PR introduces new public parameters (mapTypeControlEnabled, fullscreenControlEnabled, streetViewControlEnabled) to the GoogleMap widget, this is a backward-compatible feature addition. According to Semantic Versioning, this requires a minor version bump (to 2.18.0) rather than a patch bump (to 2.17.2). Additionally, because google_maps_flutter now uses the new fields of MapConfiguration introduced in google_maps_flutter_platform_interface, you must update the dependency on google_maps_flutter_platform_interface in this pubspec.yaml to require the new version (e.g., ^2.16.0). Otherwise, compilation will fail if an older version of the platform interface is resolved.

version: 2.18.0

[gemini-code-assist]

Because google_maps_flutter_web now uses the new fields of MapConfiguration in convert.dart, you must update its dependency on google_maps_flutter_platform_interface in this pubspec.yaml to require the new version (e.g., ^2.16.0). Otherwise, compilation will fail if an older version of the platform interface is resolved.