-
Notifications
You must be signed in to change notification settings - Fork 152
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
Change GoogleMap() content parameter default to {} and make content non-nullable #493
Labels
priority: p4
An issue that should be addressed eventually.
released
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
Comments
bubenheimer
added a commit
to bubenheimer/android-maps-compose
that referenced
this issue
Jan 1, 2024
…ntent non-nullable Fixes googlemaps#493
bubenheimer
added a commit
to bubenheimer/android-maps-compose
that referenced
this issue
Jan 1, 2024
…ntent non-nullable Fixes googlemaps#493
bubenheimer
added a commit
to bubenheimer/android-maps-compose
that referenced
this issue
Jan 3, 2024
…ntent non-nullable Fixes googlemaps#493
bubenheimer
added a commit
to bubenheimer/android-maps-compose
that referenced
this issue
Jan 10, 2024
…ntent non-nullable Fixes googlemaps#493
bubenheimer
added a commit
to bubenheimer/android-maps-compose
that referenced
this issue
Feb 1, 2024
…ntent non-nullable Fixes googlemaps#493
googlemaps-bot
pushed a commit
that referenced
this issue
May 7, 2024
# [5.0.0](v4.4.2...v5.0.0) (2024-05-07) ### Bug Fixes * fixed documentation ([#567](#567)) ([31960a2](31960a2)) ### Features * change GoogleMap() content parameter default to {} and make content non-nullable ([#521](#521)) ([8e5e3a6](8e5e3a6)), closes [#493](#493) ### BREAKING CHANGES * Adds optional contentDescriptor parameter to MarkerComposable and AdvancedMarker. Makes content parameter of GoogleMap non-nullable, but with an empty default value.
🎉 This issue has been resolved in version 5.0.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
priority: p4
An issue that should be addressed eventually.
released
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
GoogleMap() currently uses
null
for a defaultcontent
parameter. This seems an unusual approach to me, plus less descriptive than using{}
and keeping the parameter non-nullable. It also slightly complicates the implementation, needing a special case for null content.Instead, use
{}
and makecontent
non-null. This is in compliance with Google Compose Component API guidelines that favor more descriptive parameter defaults over null defaults.The text was updated successfully, but these errors were encountered: