farshadtahmasbi / vita Goto Github PK

Can I use it with Java code ?

Hello,

As said in the title - Can the shared ViewModel be attached to only Fragment's lifecycle, not to activity's lifecycle?

I have checked readme and peeked at the code, but I am not sure if such functionality works as I described. For now it it the biggest issue for me: when I enter some fragments with steps I want to share LiveData. When I leave all of the fragments for some reason (quiting or finishing all steps) I want to see ViewModel being destroyed to keep memory free + reset data which is not needed now. When it is attached to the activity then when I re-enter steps, I will get shared ViewModel with live data that is already set, which is not the thing I want

Greetings,
Janusz

https://developer.android.com/studio/build/jcenter-migration

Hi,
Vita is defined as a lib to share ViewModels across activity or make them global at App level.
But can it be used a state container / single source of truth for Android? Quoting web frameworks (sorry for that) can Vita be the Redux/Vuex for Android ecosystem?

More specifically: in case of a ViewModel with No Owner (shared across all application) is there a way to lazy load only the parts of the ViewModel that are needed at a certain point to avoid fat ViewModel?

You could say just use a regular ViewModel for that fragment/activity, but what if I need the same ViewModel with te same info (e.g. the logged user and I do not want to use sharedPrefs) at different places in my app? Is it possible to modularize the ViewModel with No Owner and load only chunks of it when needed?

Thanks!

How about mapping ViewModelStoreOwner for compose?