chore: Use existing loadAvatar method instead of loadUserAvatar

Infomaniak · Feb 21, 2025 · cbc142a · cbc142a
1 parent f9f42b4
commit cbc142a
Showing 1 changed file with 1 addition and 6 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
@@ -196,7 +196,7 @@ class AvatarView @JvmOverloads constructor(
     ) {
         when (avatarDisplayType) {
             AvatarDisplayType.UNKNOWN_CORRESPONDENT -> loadUnknownUserAvatar()
-            AvatarDisplayType.USER_AVATAR -> loadUserAvatar(correspondent!!, bimi)
+            AvatarDisplayType.USER_AVATAR -> AccountUtils.currentUser?.let { loadAvatar(user = it) }
             AvatarDisplayType.CUSTOM_AVATAR,
             AvatarDisplayType.INITIALS -> loadAvatarUsingDictionary(correspondent!!, contacts, bimi)
             AvatarDisplayType.BIMI -> loadBimiAvatar(correspondent!!, bimi!!)
@@ -230,11 +230,6 @@ class AvatarView @JvmOverloads constructor(
         binding.avatarImage.baseLoadAvatar(correspondent = mergedContact ?: correspondent)
     }
 
-    private fun loadUserAvatar(correspondent: Correspondent, bimi: Bimi?) {
-        state.update(correspondent, bimi)
-        binding.avatarImage.baseLoadAvatar(correspondent)
-    }
-
     private fun ImageView.baseLoadAvatar(correspondent: Correspondent) {
         if (correspondent.shouldDisplayUserAvatar()) {
             this@AvatarView.loadAvatar(AccountUtils.currentUser!!)