RFC: Remove experimental MapEffect composable #267
Labels
needs more info
This issue needs more information from the customer to proceed.
priority: p3
Desirable enhancement or fix. May not be included in next release.
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
If you would like to recommend against this proposal, please comment below or react with 👎 .
MapEffect was added in #140 to expose the underlying GoogleMap Maps SDK object to enable extension and usages such as clustering with the utility library.
With Compose-native clustering being added by #258, we're hoping that MapEffect is no longer needed. Providing direct access to the map is potentially buggy as noted in this comment.
It seems like MapEffect would still be necessary for other Android Maps Utils such as GeoJSON layer (#29) and KML layer (#129).
Please comment below if you have other use cases that would require exposing the map object.
The text was updated successfully, but these errors were encountered: