speaking of navigation, should something like this...

# compose

[bryansills]

speaking of navigation, should something like this work?

@Composable
fun BasicNav() {
    var isLoggedIn by remember { mutableStateOf(false) }
    NavHost(startDestination = "Profile") {
        composable("Profile") { Profile(isLoggedIn) { isLoggedIn = !isLoggedIn } }
        composable("Dashboard") { Dashboard() }
        if (isLoggedIn) {
            composable("Scrollable") { Scrollable() }
        }
    }
}

(the lambda passed into Profile()) is just connected to a Button to toggle the logged in state

[Ian Lake]

This sounds suspiciously like the same issue mentioned here: https://kotlinlang.slack.com/archives/CJLTWPH7S/p1601232258162100?thread_ts=1601232258.162100&cid=CJLTWPH7S

[Ian Lake]

The underlying issue that Mark filed, https://issuetracker.google.com/issues/169471826, is still open and assigned to @Leland Richardson [G]

[bryansills]

yeah it is. lifting the state up to a higher level made the conditional navigation graph work.

[bryansills]

this type of code (where you define state locally) works in react. it would be nice to work in compose land.

[bryansills]

but super glad that the nav stuff already has some of this functionality working.