update method

README.md

@@ -33,7 +33,7 @@ MVI-Dispatcher 应运而生。
 在本案例中，我将为您展示，MVI-Dispatcher 是如何将原本 "繁杂易出错" 消息分发流程，通过 **寥寥几行代码** 轻而易举完成。
 
 ```Groovy
-implementation 'com.kunminx.arch:mvi-dispatch-ktx:7.2.0'
+implementation 'com.kunminx.arch:mvi-dispatch-ktx:7.3.0'
 ```
 
  
@@ -94,7 +94,7 @@ MVI-Dispatcher 应运而生，
 
 # Thanks to
 
-感谢小伙伴苏旗的测试反馈和协助排查
+感谢小伙伴苏旗、YJH 的测试反馈
 
 [AndroidX](https://developer.android.google.cn/jetpack/androidx)
 

README_EN.md

@@ -31,7 +31,7 @@ The author has long focused on the "business architecture" pattern and is commit
 In this case, I will show you how MVI-Dispatcher can easily accomplish the previously complicated and error-prone message distribution process with just a few lines of code.
 
 ```Groovy
-implementation 'com.kunminx.arch:mvi-dispatch-ktx:7.2.0'
+implementation 'com.kunminx.arch:mvi-dispatch-ktx:7.3.0'
 ```
 
  

build.gradle

@@ -2,8 +2,8 @@ buildscript {
   ext {
     appTargetSdk = 32
     appMinSdk = 15
-    appVersionCode = 702000
-    appVersionName = "7.2.0"
+    appVersionCode = 703000
+    appVersionName = "7.3.0"
     room_version = '2.4.3'
   }
 }

mvi-dispatch/src/main/kotlin/com/kunminx/architecture/domain/dispatch/MviDispatcherKTX.kt

@@ -33,14 +33,14 @@ open class MviDispatcherKTX<T : Any> : ViewModel(), DefaultLifecycleObserver {
   }
 
   fun output(activity: AppCompatActivity?, observer: (T) -> Unit) {
-    output(activity, observer)
+    outputTo(activity, observer)
   }
 
   fun output(fragment: Fragment?, observer: (T) -> Unit) {
-    output(fragment?.viewLifecycleOwner, observer)
+    outputTo(fragment?.viewLifecycleOwner, observer)
   }
 
-  private fun output(lifecycleOwner: LifecycleOwner?, observer: (T) -> Unit) {
+  private fun outputTo(lifecycleOwner: LifecycleOwner?, observer: (T) -> Unit) {
     currentVersion = version
     observerCount++
     lifecycleOwner?.lifecycle?.addObserver(this)