sindrenm
03/16/2022, 11:22 AMViewModelStoreOwner
, which might be a nav back stack entry or a fragment or whatnot, but not an “actual” composable, if that makes sense. However, if I have a list of similar items and I want each of them to have their own instance of a same-type View Model, then I'm at a loss on how to achieve this. Any suggestions?curioustechizen
03/16/2022, 11:25 AMsindrenm
03/16/2022, 11:44 AMcurioustechizen
03/16/2022, 11:45 AMZach Klippenstein (he/him) [MOD]
03/16/2022, 2:41 PMViewModel
at all then? Just use a regular class.sindrenm
03/16/2022, 3:02 PMviewModelScope
.Zach Klippenstein (he/him) [MOD]
03/16/2022, 3:06 PMsindrenm
03/16/2022, 3:07 PMArun Joseph
03/17/2022, 1:42 PMgetViewModel
sindrenm
03/18/2022, 8:38 AM@EntryPoint
, which seems to work the way it should. Most of the reason for using Jetpack ViewModels so far has been for the convenience of @HiltViewModel
, `viewModel()`/`hiltViewModel()` and having that just automatically work, but it wasn't too much extra work to tie a regular class into Hilt and whatnot, so we might end up doing this forward. 👍