I have noticed some composables have a content field, and they also have a body for content. Should ...

# compose

[Mehdi Haghgoo]

I have noticed some composables have a content field, and they also have a body for content. Should the children composables go in their content field or written in their body?
For example surface:

@Composable
fun Surface(
    modifier: Modifier = Modifier,
    shape: Shape = RectangleShape,
    color: Color = MaterialTheme.colors.surface,
    contentColor: Color = contentColorFor(color),
    border: Border? = null,
    elevation: Dp = 0.dp,
    content: @Composable () -> Unit
)

[allan.conda]

and they also have a body for content

What do you mean?

[romainguy]

When a lambda (content here) is the last parameter you can use a special Kotlin syntax so you can write Surface { content() } instead

[romainguy]

(trailing lambda)

[allan.conda]

ah so that’s what he meant, 😄

[Mehdi Haghgoo]

@romainguy so all composables we write inside the body of other composables are made possible thanks to trailing lambdas?

[matvei]

Yes, the "body" of the composable is possible and equal to the last parameter of this composable is a lambda

https://kotlinlang.org/docs/reference/lambdas.html#passing-a-lambda-to-the-last-parameter

[caelum19]

Also see this : https://kotlinlang.org/docs/reference/type-safe-builders.html
K K K K