如何将Fragment中的文本校验逻辑提取至ViewModel？

Great question! Moving that comparison logic into the ViewModel aligns perfectly with MVVM principles, keeping your Fragment focused solely on UI concerns. Here's how to do it cleanly:

Step 1: Refactor the ViewModel #

We'll encapsulate the comparison logic inside the ViewModel by creating a dedicated method to handle text input from the EditText. This way, the ViewModel controls when the quoteAuthor state gets updated, eliminating the need for the Fragment to handle business logic.

class YourViewModel : ViewModel() {
    // Private mutable LiveData for internal state management
    private val _quoteAuthor = MutableLiveData<String>()
    // Public immutable LiveData for the Fragment to observe
    val quoteAuthor: LiveData<String> = _quoteAuthor

    // Method to process input from the EditText
    fun updateQuoteAuthor(inputText: String?) {
        inputText?.trim()?.let { cleanedText ->
            // The comparison logic now lives in the ViewModel
            if (_quoteAuthor.value != cleanedText) {
                _quoteAuthor.value = cleanedText
            }
        }
    }
}

Step 2: Simplify the Fragment Code #

Now your Fragment only needs to forward text changes to the ViewModel and observe the updated state—no more conditional checks here:

// Forward EditText changes to the ViewModel
etAuthorName.doAfterTextChanged { editable ->
    viewModel.updateQuoteAuthor(editable?.toString())
}

// Observe the ViewModel's state and update the UI directly
viewModel.quoteAuthor.observe(viewLifecycleOwner) { authorName ->
    etAuthorName.setText(authorName)
}

Why This Works #

• Separation of Concerns: The ViewModel handles state logic (when to update the author name), while the Fragment only manages UI interactions.
• Avoids Infinite Loops: By checking if the input differs from the current state before updating, we prevent the observe callback from triggering another text change event.
• Testability: You can now unit test the updateQuoteAuthor method independently to verify the comparison logic works as expected.

内容的提问来源于stack exchange，提问作者Morozov