Chris Arriola

No plans yet but `Places Compose` would be nice 👍

This is what `MarkerDragState` is for. You should be able to do the following: ``` val markerDragState = rememberMarkerDragState() GoogleMap() { Marker( draggable = true, markerDragStae = markerDragState, // ......

> I think it doesn't need to be a callback style if the drag state has marker object or position info. Yeah, this is what I'm thinking as well. There...

Please see my comment on https://github.com/googlemaps/android-maps-compose/pull/11#issuecomment-1035586376 for how this feature should be implemented.

@bubenheimer thanks for the feedback on the current marker drag API. I'm a bit confused what you mean by information loss as all marker drag transition states should be reported...

I'm not able to repro this in the sample app. Can you share a snippet of your implementation?

Yes, I would like to add this! Adding clustering support isn't quite that simple though as Maps Compose entirely manages the underlying `GoogleMap`. I've summarized my thoughts on this in...

Looks like there are 2 causes for the failed actions linked in the description: 1. Failure due to secrets not being available on forks. This is the reason for the...

Quickest is to expose a function in `CameraPositionState` although that won't to be the right place to do so. A state holder object like `GoogleMapState` that contains `CameraPositionState` etc. would...

@recoverrelax you can use `MapEffect` to get the snapshot. Something like: ``` GoogleMap { MapEffect { map -> map.snapshot { snapshot -> // Got snapshot here } } } ```