-
Notifications
You must be signed in to change notification settings - Fork 165
feat: added BitmapDescriptor as parameter to AdvancedMarker #718
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
Conversation
Code Coverage
|
| } | ||
| update(pinConfig) { | ||
| if (iconView == null) { | ||
| if (icon == null && iconView == null) { |
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.
Is this correct? Do you need the icon to be set to proceed? I am not sure about this code.
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.
In order of priority we set the iconView, then the pinConfig and then the icon. This is to cover the case where many parameters are set at once.
I have added a comment to clarify this.
| // 3. If neither iconView nor pinConfig are available, fall back to the raw icon. | ||
|
|
||
| if (iconView != null) { | ||
| advancedMarkerOptions.iconView(iconView) |
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.
Nit: these multibranch conditionals typically read better as a when statement
# [6.7.0](v6.6.0...v6.7.0) (2025-07-14) ### Features * added BitmapDescriptor as parameter to AdvancedMarker ([#718](#718)) ([e1c2277](e1c2277))
|
🎉 This PR is included in version 6.7.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
The following PR adds a new parameter BitmapDescriptor to the AdvancedMarker. The AdvancedMarker has, as an addition to the Marker, the possibility to set up an iconView, a pinConfig and/or the CollisionBehavior. It could be that users only want to control the CollisionBehavior, so this interface could be useful.
Fixes #708 🦕