-
Notifications
You must be signed in to change notification settings - Fork 142
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
feat: customize Marker using Composable #355
Conversation
maps-compose/src/main/java/com/google/maps/android/compose/Marker.kt
Outdated
Show resolved
Hide resolved
val compositionContext = rememberCompositionContext() | ||
val currentContent by rememberUpdatedState(content) | ||
|
||
return remember(parent, compositionContext, currentContent, *keys) { |
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.
We are having a funny error here since the vararg is not properly resolved, but does not seem to affect the compilation and we can probably live with it.
maps-compose/src/main/java/com/google/maps/android/compose/Marker.kt
Outdated
Show resolved
Hide resolved
@mosmb , thanks for the contribution, it looks great! I left a couple of comments, let me know what you think. |
@kikoso |
LGTM! Thanks for the contribution, @mosmb ! |
app/src/main/java/com/google/maps/android/compose/BasicMapActivity.kt
Outdated
Show resolved
Hide resolved
@kikoso |
@kikoso |
Hi @mosmb ! It is a topic more complex. The instrumentation tests are running on your branch, and you would need to set up the API Key for them to work. There are a couple of approaches that can fix this, but they might pose a security risk (see https://securitylab.github.com/research/github-actions-preventing-pwn-requests/). We are currently exploring this. In the meantime, adding the API Key as a secret in your repository should work out. What we generally do is to run the test before getting any PR merged, but this is something that we want to fix so any external PRs can properly report any failure on an instrumentation test. |
@kikoso |
@kikoso Tests seem to fail because of the API key |
@kikoso |
Hi @mosmb ! We have a couple of PRs that we want to merge first and release a new version, but this should happen rather imminently. |
@kikoso Ok! Thank you for the information! |
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.
Thank you for contributing this highly requested feature, @mosmb! Although the github action can't access the secrets to run tests on GitHub, would you still please add tests for the new functionality to keep our code coverage even? We'll be able to merge this PR when that task is done.
Thank you @wangela for your feedback! |
# [2.14.0](v2.13.1...v2.14.0) (2023-08-17) ### Features * customize Marker using MarkerComposable ([#355](#355)) ([51bb2bf](51bb2bf))
🎉 This PR is included in version 2.14.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
@WonderCsabo In some cases, the |
@mosmb , which utility method do you mean? We are working on some stuff for next month, but I would like to upgrade Compose as one of the next issues. |
@kikoso |
Fixes #41 🦕