I have a question, how does a Composable function ...

# compose

[molikto]

I have a question, how does a Composable function with a non-Unit return value works? Will the result of that function call be cached if the Composable function parameters doesn't change? I've found this pattern for Dialog works pretty well. It returns a MutableState so code outside can mutate it to show the dialog

Untitled

[Adam Powell]

@Leland Richardson [G] can speak to the precise skipping rules, I believe they're about to change a bit but it shouldn't affect what you're doing here.

[Adam Powell]

Either way we consider it better to pass in this kind of state as a parameter rather than returning a control surface

[Adam Powell]

By offering it as a parameter it's clearer that the surrounding environment is controlling the dialog's behavior and that that surrounding environment owns that state

[Adam Powell]

It also doesn't impose ordering requirements on the caller; the caller can pass that kind of state to other things before invoking the InputDialog if it would make more sense/be clearer to do so

[Adam Powell]

For dialogs in particular we've found it's quite nice to bring the conditional logic of showing the dialog out of the dialog functions entirely, e.g.:

var shown by savedInstanceState { false }

if (shown) {
    InputDialog(...)
}

[Adam Powell]

So that when the dialog enters composition, it's shown, and when it leaves composition, it's dismissed