From 135e7ab13bfab6f1a0f045010c88e8d0de84807f Mon Sep 17 00:00:00 2001 From: madroid Date: Wed, 18 May 2022 21:40:47 +0800 Subject: [PATCH] Rename following to interests in ArchitectureLearningJourney.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit follow this commit： https://github.com/android/nowinandroid/commit/dc4af7e6f7795444ceddd8ee5dd91be679cae4e4 --- docs/ArchitectureLearningJourney.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/ArchitectureLearningJourney.md b/docs/ArchitectureLearningJourney.md index dd0715028..1a5112058 100644 --- a/docs/ArchitectureLearningJourney.md +++ b/docs/ArchitectureLearningJourney.md @@ -276,7 +276,7 @@ View models receive streams of data as cold [flows](https://kotlin.github.io/kot **Example: Displaying followed topics and authors** -The `FollowingViewModel` exposes `uiState` as a `StateFlow`. This hot flow is created by combining four data streams: +The `InterestsViewModel` exposes `uiState` as a `StateFlow`. This hot flow is created by combining four data streams: @@ -287,7 +287,7 @@ The `FollowingViewModel` exposes `uiState` as a `StateFlow`. T The list of `Author`s is mapped to a new list of `FollowableAuthor`s. `FollowableAuthor` is a wrapper for `Author` which also indicates whether the current user is following that author. The same transformation is applied for the list of `Topic`s. -The two new lists are used to create a `FollowingUiState.Interests` state which is exposed to the UI. +The two new lists are used to create a `InterestsUiState.Interests` state which is exposed to the UI. ### Processing user interactions @@ -296,7 +296,7 @@ User actions are communicated from UI elements to view models using regular meth **Example: Following a topic** -The `FollowingScreen` takes a lambda expression named `followTopic` which is supplied from `FollowingViewModel.followTopic`. Each time the user taps on a topic to follow this method is called. The view model then processes this action by informing the topics repository. +The `InterestsScreen` takes a lambda expression named `followTopic` which is supplied from `InterestsViewModel.followTopic`. Each time the user taps on a topic to follow this method is called. The view model then processes this action by informing the topics repository. ## Further reading