I am using version 5.0.4 of this library. On my map, I need to add a composable marker which I am doing via MarkerComposable. This composable is marked with @GoogleMapComposable that should enforce correct usage (introduced in #130). I think there is an issue here as this gets triggered if I use a standard/non maps composable inside the MarkerComposable as this is then not marked with the @GoogleMapComposable annotation. Probably, there should be an exclude for this specific case as I cannot annotate all composables that I want to use with that annotation (for example a simple Text). Or is there a simple way to suppress it?
For me, this is quite annoying as we enforce our builds to not have any warnings.
Steps to reproduce
- Use some composable (Card, Text, ...) inside the
MarkerComposable
- The build warning "Calling a Google Map Composable composable function where a UI Composable composable was expected" is triggered
Code example
MarkerComposable( // <-- has the @GoogleMapComposable annotation
// ...
) {
Text(text = "Hello World") // <-- does not have the @GoogleMapComposable annotation, but is a valid use case
}
I am using version 5.0.4 of this library. On my map, I need to add a composable marker which I am doing via
MarkerComposable. This composable is marked with@GoogleMapComposablethat should enforce correct usage (introduced in #130). I think there is an issue here as this gets triggered if I use a standard/non maps composable inside theMarkerComposableas this is then not marked with the@GoogleMapComposableannotation. Probably, there should be an exclude for this specific case as I cannot annotate all composables that I want to use with that annotation (for example a simpleText). Or is there a simple way to suppress it?For me, this is quite annoying as we enforce our builds to not have any warnings.
Steps to reproduce
MarkerComposableCode example