Is it ok to set state type as a lambda? (`MutableState<(() -> Unit)?>`) I've been thinking...

# compose

[bitkiller]

Is it ok to set state type as a lambda? (MutableState<(() -> Unit)?>)

I've been thinking about doing some kind of "confirmation dialog decorator" (confirmation or other, e.g. "request pin") for some user actions. It would be used like

var confirmationDialog: (() -> Unit)? by remember {
    mutableStateOf(null)
}

if (confirmationDialog != null) {

    Dialog(onOk = {
        confirmationDialog?.invoke()
        confirmationDialog = null
    }, onCancel = {
        confirmationDialog = null
    })
}

SaveButton(
  onClick = requireConfirmation { theRealSave() }
)

Is it too hacky? Any issue other issue?

[Zach Klippenstein (he/him) [MOD]]

yea that’s fine, you can always create a type alias or fun interface if you find the function type to be too cryptic

[bitkiller]

thanks. it works, but feels strange.

[louiscad]

It's perfectly fine to put lambdas in MutableState, that's how I bridge coroutines reliant UI abstractions with state driven composables.