You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: reactivestate-android/README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Module reactivestate-android
2
2
3
-
APIs mostly useful for classic Android Fragment/Activity.
3
+
APIs mostly useful for legacy Android Fragment/Activity. You should prefer the APIs in reactivestate-core and reactivestate-compose instead.
4
4
5
5
## Event handling
6
6
@@ -256,9 +256,9 @@ These are the building blocks for your own lifecycle-aware components which can
256
256
Finally, with `validUntil()` you can define properties that only exist during a certain lifecycle subset and are dereference their value outside of that lifecycle subset.
257
257
This can get rid of the ugly [boilerplate](https://developer.android.com/topic/libraries/view-binding#fragments) when working with view bindings, for example.
258
258
259
-
## Multiplatform ViewModel example
259
+
## ViewModel example
260
260
261
-
This library allows creating multiplatform ViewModels (inherited from `BaseReactiveState`) and also provides a `by reactiveState` helper for attaching it to Android's `Activity` or `Fragment` with proper lifecycle handling.
261
+
This library allows creating ViewModels (inherited from `BaseReactiveState` - not to be confused with the new `ReactiveViewModel` API) and also provides a `by reactiveState` helper for attaching it to Android's `Activity` or `Fragment` with proper lifecycle handling.
262
262
263
263
```kotlin
264
264
// This is a multiplatform "ViewModel". It doesn't inherit from Android's ViewModel
0 commit comments