which is this a product of viewModelStore leaking lifecycle details as soon as you try to do DI and the solution was a mountain of dagger magic rather then fixing the view model library impl? and doesn’t an activity or fragment knowing about the scope(specific store owner) of a viewmodel violate inversion of control

all of which to say I think hilt is doubling down to bandaid over a design issue in viewmodel rather then making library integration of viewmodel a bit harder to actually fix the root issue?