Has anyone ran into issues with a viewmodel directly invoking a navcontroller? The handoff for navigation between a fragment and viewmodel is not at all elegant so I'm thinking about just injecting the navcontroller into the viewmodel but I'm having a hard time finding references that support that idea

the NavHostFragment creates the NavController with the context present in onCreate so I would expect that you wouldn't want to hold a hard reference to a nav controller unless you created it manually with the application context as the argument. otherwise memory leaks would be a thing

Gotcha, using the navcomponent with a viewmodel and livedata feels quite awkward

view model ends up being a super leaky abstraction due to it rafting across points in the fragtivity lifecycle. so even though the attempt is to break away from it, you still have to be innately aware of the lifecycle. live data to me is, pointless for lack of a better word... so many other reactive api's already in the wild at that point, which when used properly make live data pointless. even without magic things like auto dispose, it is straightforward to respect the lifecycle

Yeah, I find myself hitting limitations of LiveData fairly often.

live data stateful by default right? so in that case it would need to be an event not a state

Yeah that's a really good point

You could also use a shared view model scoped to a graph to handle the navigation. Such a VM would live through the graph lifecycle and hold the right screen in a Livedata

I worry that would create more problems than it'd solve. The other ViewModels would need reference to that ViewModel so they can pass navigation arguments to it.

Hey @Cody Engel, I also faced this issue initially. Wanted to use LiveData to for exposing events to the view, but LiveData being made for representing a last value, makes it not a fit for events. What would be a really nice option that goes with coroutines is

Flow

. So I would have something like

interface ViewModel {

    val navigateToChatScreenEvents: Flow<NavigateToChatScreenEvent>

    object NavigateToChatScreenEvent

}