A modern programming language that makes developers happier.

kotlinlang

I was just exploring on Compose navigation. So, we have the following for scoping ViewModel to the destination.
```val exampleViewModel = hiltNavGraphViewModel&lt;ExampleViewModel&gt;()```
However, I couldn’t find anything or any info on passing a `ViewModelProvider.Factory` above (in case there are parameters for the ViewModel constructor).
Am I missing something or is it yet to be developed?

You should check <https://dagger.dev/api/latest/dagger/hilt/android/lifecycle/HiltViewModel.html|@HiltViewModel annotation> and Hilt/navigation documentation for Compose <https://developer.android.com/jetpack/compose/libraries#hilt|here>

So the key is to use `viewModel()` instead right?

<@U01BDD3U273> this isn't using any di, but might help:
```        composable(
            "${Screen.PlayerScreen.route}/{id}",
            arguments = listOf(navArgument("id") { type = NavType.IntType })
        ) {
            val arguments = requireNotNull(it.arguments)
            val playersViewModel = viewModel&lt;PlayersViewModel&gt;(
                factory = PlayersViewModelFactory(
                    it,
                    PlayersRepository(),
                    arguments
                )
            )
            PlayersScreen(playersViewModel)
        }```

Thanks <@U014N6FP4KT>. One question however, doesn’t Hilt get the dependencies when simply using `viewModel()`. My ViewModel has few dependencies in its constructor that Hilt is supposed to provide. Using `hiltNavGraphViewModel` inside `composable` destination just works out of the box. However, if I use simply `viewModel()` , it throws Runtime exception that it can’t create an instance of the ViewModel.

The docs however states that it should fulfil all the dependencies while using `viewModel()`. :thinking_face:

Are you using hilt-navigation-compose artifact ?

This one: <https://developer.android.com/jetpack/androidx/releases/hilt#hilt-navigation-compose-1.0.0-alpha01>

If you are using a HiltViewModel, you must use their factory. That's what `hiltNavGraphViewModel()` does - automatically uses the right factory for you. If you're not using Hilt, then use `viewModel()` and pass it your custom factory, which it takes as an optional parameter

Thanks for the help. Will explore more around it.

@/Ian Lake Does the documentation need updating?
&gt; The `viewModel()` function mentioned in the ViewModel section automatically uses the ViewModel that Hilt constructs with the `@HiltViewModel` annotation. We’ve provided documentation with information about <https://developer.android.com/training/dependency-injection/hilt-jetpack#viewmodels|Hilt's ViewModel integration>.
<https://developer.android.com/jetpack/compose/libraries#hilt>

ah, we need to use it if we’re using compose navigation
&gt; If your `@HiltViewModel` annotated `ViewModel` is <https://developer.android.com/guide/navigation/navigation-programmatic#share_ui-related_data_between_destinations_with_viewmodel|scoped to the navigation graph>, use the `hiltNavGraphViewModel` composable function that works with fragments or activities that are annotated with `@AndroidEntryPoint`.