From 2c7c720a4d98a324f87d80b20337a7eb4b2477bb Mon Sep 17 00:00:00 2001 From: Andy Scherzinger Date: Sat, 17 Aug 2024 19:56:45 +0200 Subject: [PATCH] fix: use layoutInflater directly Signed-off-by: Andy Scherzinger --- .../java/com/nextcloud/talk/ui/dialog/DialogBanListFragment.kt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/src/main/java/com/nextcloud/talk/ui/dialog/DialogBanListFragment.kt b/app/src/main/java/com/nextcloud/talk/ui/dialog/DialogBanListFragment.kt index 074bf4843..0b3d83c16 100644 --- a/app/src/main/java/com/nextcloud/talk/ui/dialog/DialogBanListFragment.kt +++ b/app/src/main/java/com/nextcloud/talk/ui/dialog/DialogBanListFragment.kt @@ -82,7 +82,7 @@ class DialogBanListFragment(val roomToken: String) : DialogFragment() { override fun onCreateView(inflater: LayoutInflater, container: ViewGroup?, savedInstanceState: Bundle?): View { NextcloudTalkApplication.sharedApplication!!.componentApplication.inject(this) - binding = FragmentDialogBanListBinding.inflate(LayoutInflater.from(context)) + binding = FragmentDialogBanListBinding.inflate(layoutInflater) viewModel = ViewModelProvider(this, viewModelFactory)[ConversationInfoViewModel::class.java] conversationUser = currentUserProvider.currentUser.blockingGet()