rememberViewModelStoreOwner

@Composable
fun rememberViewModelStoreOwner(
    provider: ViewModelStoreProvider,
    key: Any? = currentCompositeKeyHashCode,
    savedStateRegistryOwner: SavedStateRegistryOwner? = LocalSavedStateRegistryOwner.current
): ViewModelStoreOwner

Remembers a ViewModelStoreOwner scoped to the current composable using an existing provider.

This function creates an owner unique to this specific call site in the composition hierarchy. While this composable is active, it maintains an active reference to the underlying ViewModelStore, preventing it from being cleared.

Note: Unlike many other scoped owners, ViewModels created with this owner are not automatically cleared simply because this composable leaves the composition. The ViewModelStore is only cleared when ViewModelStoreProvider.clearKey is explicitly called for this key.

This function is responsible for releasing its reference to the store when it leaves the composition, allowing the provider to perform cleanup if the store has been marked for clearing.

@Composable
fun rememberViewModelStoreOwner(
    parent: ViewModelStoreOwner? = checkNotNull(LocalViewModelStoreOwner.current) {
            "CompositionLocal LocalViewModelStoreOwner not present"
        },
    savedStateRegistryOwner: SavedStateRegistryOwner? = LocalSavedStateRegistryOwner.current,
    defaultArgs: SavedState = savedState(),
    defaultCreationExtras: CreationExtras = parent.defaultViewModelCreationExtras,
    defaultFactory: ViewModelProvider.Factory = parent.defaultViewModelProviderFactory
): ViewModelStoreOwner

Remembers a ViewModelStoreOwner scoped to the current composable.

This function creates an owner that is unique to this specific call site in the composition hierarchy. It allows creating ViewModels that are strictly scoped to this composable's lifecycle: they are created when this composable enters the composition and cleared immediately when it leaves.

The owner is linked to the parent, ensuring that configuration changes (like rotation) are handled correctly: the ViewModels survive rotation if the parent does, but are destroyed if the parent is destroyed.

Null parent: If parent is EXPLICITLY null, this creates a root provider that runs independently. By default, it requires a parent from the LocalViewModelStoreOwner and will throw an IllegalStateException if one is not present.