Having a composable A which is a Column, If you create a composable B with three Text elements, and ...

# compose

[Pablo]

Having a composable A which is a Column, If you create a composable B with three Text elements, and these Texts are not in a column in the composable B, is an acceptable approach to not wrap the 3 Texts into a column because you are going to use the composable B into a composable with a Column? or is preferable to wrap them into a Column even if you are going to put that composable into another composable with a Column?

[Chrimaeon]

pass the ColumnScope to the Composable so its clear its context is a Column i.e.

@Composable
fun ColumnScope.MyTexts() {}

you will also need it if you want to apply Column specific modifiers to your Text composables

[Pablo]

is not preferable to simply wrap the texts into another column?

[Pablo]

for simplicity

[Chrimaeon]

but why would you need the parent column then?

[Pablo]

yes, in the parent there are more items

[Pablo]

other buttons, other panels, etc...

[Pablo]

I'm just reorganizing them in groups

[Pablo]

to reduce the function size

[Chrimaeon]

then do whatever you prefer. I’d go with the ColumnScope approach. 🤷🏼

[Pablo]

thank you