So I have the following snippet for a check box item

@Composable
fun CheckBoxItem(
    modifier: Modifier = Modifier,
    checked: Boolean,
    label: String,
    onCheckedChange: (Boolean) -> Unit,
    enabled: Boolean = true,
    trailIcon: @Composable (RowScope.() -> Unit)? = null,
) {
    Row(
        modifier = modifier
            .fillMaxWidth()
            .height(56.dp)
            .toggleable(
                value = checked,
                onValueChange = onCheckedChange,
                role = Role.Checkbox,
   enabled = enabled
            ),
        verticalAlignment = Alignment.CenterVertically,
    ) {
        Text(
            modifier = Modifier.weight(1f),
            text = label,
            style = MaterialTheme.typography.bodyLarge,
        )
        Checkbox(
            checked = checked,
            onCheckedChange = null,
            enabled = enabled
        )
        if (trailIcon != null) trailIcon()
    }
}

I went for the slot approach to allow callers of this funciton to better define the trailing icons they want to set. However this means now that the enabled parameter will not take effect on that slow ( leaving the responibility ont eh caller which seems annoying). Should I wrap the trailing icon lamba in another row and play with the gestures or is the slot pattern not the way to go here?

I guess since they have to pass the is enabled param anyways they can use it when defining the lambda as well 🤷