How do I correctly create a ViewModel in a `ComponentDialog` (not `DialogFragment`)? There is no `by...

# android

[Lukasz Kalnik]

How do I correctly create a ViewModel in a ComponentDialog (not DialogFragment)? There is no by viewModels().

[marlonlom]

you mean bind the viewmodel?

[Lukasz Kalnik]

Yes

[Lukasz Kalnik]

Create a reference to it inside the ComponentDialog

[marlonlom]

Check this from stackoverflow :
https://stackoverflow.com/questions/59212981/viewmodel-in-dialogfragment

[Lukasz Kalnik]

Yes, but ComponentDialog doesn't extend DialogFragment

[Lukasz Kalnik]

I suppose it's not possible for a ComponentDialog to have its own ViewModel, as ComponentDialog is not a ViewModelStoreOwner.

[marlonlom]

mmm, i think you can provide an extension or a delegate function for getting the viewmodel

[Lukasz Kalnik]

How?

[Lukasz Kalnik]

This is possible only in `Fragment`s and `Activity`s

[Lukasz Kalnik]

Not in a Dialog

[marlonlom]

Did you have this line when creating the viewmodel instance in DialogFragment?

private val viewModel by viewModels<SomeViewModel>(ownerProducer = { this.requireParentFragment() })

[marlonlom]

the previous comment is based on this link: https://www.linkedin.com/pulse/share-fragment-scoped-view-model-child-fragments-albert/

[Lukasz Kalnik]

I don't use a DialogFragment

[Lukasz Kalnik]

I use a ComponentDialog, which doesn't extend the DialogFragment (or Fragment)

[Lukasz Kalnik]

It has no viewModels() extension function

[marlonlom]

ah, what dependencies related to the viewmodel aspect do you have in app's build.gradle?

[marlonlom]

check if you can add this library:

implementation "androidx.lifecyclelifecycle viewmodel ktx2.2.0-rc03"

kapt "androidx.lifecyclelifecycle compiler2.2.0-rc03"

[Lukasz Kalnik]

I have these dependencies in project. It seems not possible. Thank you for your efforts.

[marlonlom]

Are you using the mentioned delegates in another fragments/activities?

[Lukasz Kalnik]

Yes, and they work

[Lukasz Kalnik]

The problem is, ComponentDialog is not a Fragment.

[Lukasz Kalnik]

It cannot have a ViewModel of its own

[Lukasz Kalnik]

Thank you for your help.

[marlonlom]

yes, i know, but, there is some ways to use the lifecycle attributes inside the component dialog.
this link explin a more bit about this: https://proandroiddev.com/dialogs-in-android-mvvm-5d6e1ca53b19
the idea is using the lifecycle observers to delegate the creation and the binding of the viewmodel

[Lukasz Kalnik]

The article only mentions `DialogFragment`s everywhere, not `Dialog`s.

[Lukasz Kalnik]

It also mentions a custom View as Dialog, but there the ViewModel is inside the Activity, which shows the dialog.

[Lukasz Kalnik]

It also uses DataBinding.

[marlonlom]

wait, dialog?
mm, where is the dialog opening/showing? in a fragment? activity?
afaik, the dialog contains callbacks for the dialog closing or the button (ok, cancel) click events, have you tried using a callback that includes the negative/positive actions and pass them in the dialog invokation?

[Ian Lake]

You need a ViewModelStoreOwner to store ViewModels, yes. A Dialog (and ComponentDialog) are at the same level as View - you'd need to go up one more layer to DialogFragment and Fragment if you want a ViewModelStoreOwner