Closed artillerymans closed 8 months ago
What are you trying to do? A ViewModel has a different lifecycle from a Composable and, as a result, a ViewModel shouldn't know or care about any lifecycles other than its own.
Because many third-party libraries use LifecycleOwner to manage the lifecycle.
Right, but your ViewModel shouldn't be consuming or need to know about other lifecycles
What are you trying to do? A ViewModel has a different lifecycle from a Composable and, as a result, a ViewModel shouldn't know or care about any lifecycles other than its own.