Allows use of ClusterManager#setAlgorithm

[matsudamper]

Is your feature request related to a problem? Please describe.
In Compose, ClusterManager is hidden internally, so ClusterManager#setAlgorithm cannot be used.

Describe the solution you'd like
Make this available.

Describe alternatives you've considered
I think it can be implemented in the following below ways.

• Pass the algorithm to Clustering Composable.
  • In the future, when all the functions available in Clustering are implemented, the number of arguments may increase.
• Add the clusterManagerFactory: () -> ClusterManager<T> argument to Clustering Composable and create it.
  • You can do everything you can do with View.
  • Bad. ClusterManager#renderer has been changed internally, causing confusion for users.
• Call the Clustering Composable with the argument onCreateClusterManager: (ClusterManager<T>) -> Unit
  • You can do everything you can do with View.
  • We believe this will be less confusing than the above because the user rewrites the behavior.
  • However, even in this case, if clusterRenderer is not specified, the behavior is internally overridden.

    • android-maps-compose/maps-compose-utils/src/main/java/com/google/maps/android/compose/clustering/Clustering.kt

      Lines 116 to 118 in 8c6c3b0

      	.collect { hasCustomContent ->
      	val renderer = clusterRenderer
      	?: if (hasCustomContent) {

• [recommend] create rememberClusterRenderer with ClusterManager as an argument.
  • Currently, clusterContent and clusterItemContent are not used when clusterRenderer is specified. I think this is complicated.
  • Prepare a low-level API using ClusterManager that can do the same thing as the View, and a high-level API.

Additional context
Our app has a large number of pins and we need to use NonHierarchicalViewBasedAlgorithm of ScreenBasedAlgorithm.

[googlemaps-bot]

🎉 This issue has been resolved in version 4.3.0 🎉

The release is available on:

• v4.3.0
• GitHub release

Your semantic-release bot 📦🚀