From ecbc35b5d6e9b9e0f2ecda586e6936ccb2d491cd Mon Sep 17 00:00:00 2001 From: NicolasBourdin88 Date: Wed, 3 Jul 2024 09:10:41 +0200 Subject: [PATCH] Use LiveData instead of MutableLiveData --- app/src/main/java/com/infomaniak/mail/views/AvatarView.kt | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/app/src/main/java/com/infomaniak/mail/views/AvatarView.kt b/app/src/main/java/com/infomaniak/mail/views/AvatarView.kt index 407619e463..eac59b3375 100644 --- a/app/src/main/java/com/infomaniak/mail/views/AvatarView.kt +++ b/app/src/main/java/com/infomaniak/mail/views/AvatarView.kt @@ -24,6 +24,7 @@ import android.util.AttributeSet import android.view.LayoutInflater import android.widget.FrameLayout import android.widget.ImageView +import androidx.lifecycle.LiveData import androidx.lifecycle.MutableLiveData import androidx.lifecycle.Observer import coil.ImageLoader @@ -62,14 +63,11 @@ class AvatarView @JvmOverloads constructor( private val state = State() // We use waitInitMediator over MediatorLiveData because we know both live data will be initialized very quickly anyway - private val avatarMediatorLiveData: MutableLiveData> = + private val avatarMediatorLiveData: LiveData> = if (isInEditMode) { MutableLiveData() } else { - Utils.waitInitMediator( - avatarMergedContactData.mergedContactLiveData, - avatarMergedContactData.isBimiEnabledLiveData, - ) + Utils.waitInitMediator(avatarMergedContactData.mergedContactLiveData, avatarMergedContactData.isBimiEnabledLiveData) } private val avatarUpdateObserver = Observer> { (contacts, isBimiEnabled) ->