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
..
BusModule.java	Contacts Activity Compose	2024-07-23 11:41:24 +02:00
ContextModule.java	Add SPDX header	2024-03-29 12:55:12 +01:00
DaosModule.kt	Offline support for conversations and chats	2024-08-12 16:47:03 +02:00
DatabaseModule.java	Offline support for conversations and chats	2024-08-12 16:47:03 +02:00
ManagerModule.kt	Message Input Refactoring	2024-06-05 17:45:01 +02:00
RepositoryModule.kt	replace userManager.currentUser usage by currentUserProvider usage	2025-02-07 13:13:38 +01:00
RestModule.java	Contacts Activity Compose	2024-07-23 11:41:24 +02:00
UtilsModule.kt	Add SPDX header	2024-03-29 15:42:11 +01:00
ViewModelModule.kt	convert rxjava to coroutines - renameRoom	2024-11-19 10:41:07 +01:00