Marcel Hibbe 5219eeb11f replace userManager.currentUser usage by currentUserProvider usage ... userManager.currentUser was called too often. I was not able to prove that a bug is related to it but i think it may fix some hidden bugs. CurrentUserProviderImpl is now used throughout the code to access the current user. userManager.currentUser is only used from CurrentUserProviderImpl whenever the _currentUser was null (should only happen on app startup) To avoid multiple initialization of CurrentUserProviderImpl it was changed to be a @Singleton The handling should soon be replaced with coroutine flows. However for the v21.0.0 release it's still done with RxJava to avoid bugs. Signed-off-by: Marcel Hibbe <dev@mhibbe.de>		2025-02-07 13:13:38 +01:00
..
data	avoid duplicated messages after sending	2025-02-05 15:56:42 +01:00
viewmodels	remove scope cancelation for handleChatOnBackPress (replace with lifecyle event)	2025-01-22 13:59:03 +01:00
ChatActivity.kt	fix shimmer and "offlineNoMessages"-info handling	2025-01-23 09:45:02 +01:00
MessageInputFragment.kt	replace userManager.currentUser usage by currentUserProvider usage	2025-02-07 13:13:38 +01:00
MessageInputVoiceRecordingFragment.kt	Message Input Refactoring	2024-06-05 17:45:01 +02:00
TypingParticipant.kt	Add SPDX header	2024-03-29 15:42:11 +01:00