As far as I remember, a ViewModel is scoped to the...

# compose

[Zhelyazko Atanasov]

As far as I remember, a ViewModel is scoped to the first parent Fragment or Activity. In an app with a single Activity and written entirely in compose, wouldn't that result in all VMs scoped to that single Activity? Or probably I misread something 🙂

[FunkyMuse]

In compose you get ViewModels scoped to the current destination

[Zhelyazko Atanasov]

Oh yes, now I remember - they can also be scoped to the current Nav Graph, so if you have sub-nav graphs, they'll be scoped to them.

[Manuel Vivo]

👍

[Manuel Vivo]

Yeah, activities, fragments, or destinations of a nav graph

[allan.conda]

And possibly in the future, scoped to the composable
https://issuetracker.google.com/issues/165642391

[Zhelyazko Atanasov]

By the way, nice overview of Jetpack Libs & Compose in your IO talk with Ian -

Using Jetpack libraries in Compose ▾

👏

[Manuel Vivo]

Thanks 🙂

[Zhelyazko Atanasov]

It will be nice to be able to scope a VM to a composable, but if that happens, I think it's going to be after 1.0 🙂

[Adam Powell]

You can, you can set up the scope the same way that navigation-compose does it using this api: https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:lifecycl[…]LocalViewModelStoreOwner.kt;l=48?q=LocalViewModel&ss=androidx

[Adam Powell]

you can do CompositionLocalProvider(LocalViewModelStoreOwner provides foo) { same as any other CompositionLocalProvider

[Zhelyazko Atanasov]

Oh nice. I'll get a closer look at the code related to all this. Thanks!