LiveData with SnackBar, Navigation and other events (the SingleLiveEvent case)
2021 Update: This guidance is deprecated in favor of the official guidelines. A convenient way for a view (activity or fragment) to communicate with a ViewModel is to use LiveData observables. The view subscribes to changes in LiveData and reacts to them. This works well for data that is displayed in a screen continuously. However, some data should be consumed only once, like a Snackbar message, a
ViewModels and LiveData: Patterns + AntiPatterns
Typical interaction of entities in an app built with Architecture ComponentsIdeally, ViewModels shouldn’t know anything about Android. This improves testability, leak safety and modularity. A general rule of thumb is to make sure there are no android.* imports in your ViewModels (with exceptions like android.arch.*). The same applies to presenters. ❌ Don’t let ViewModels (and Presenters) know abou
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
View actions (snackbar, activity navigation, ...) in ViewModel · Issue #63 · android/architecture-components-samples
