Separate library to multiple artifacts about moko-mvvm HOT 6 CLOSED

Suggested modules:

• mvvm-viewmodel (viewmodel, eventdispatcher)
• mvvm-livedata (livedata, transform, state)
• mvvm-databinding (all databinding, depends on viewmodel, livedata)
• mvvm (depends on all modules)

from moko-mvvm.

I would also like to see the equivalent for https://developer.android.com/jetpack/compose/state#viewmodel-and-jetpack-compose

from moko-mvvm.

@ln-12 what exactly you like to see? moko-mvvm provide original jetpack's viewmodels, so all integration with compose is already available

from moko-mvvm.

@Alex009 For example the ViewModel for login feature section in the readme only deals with data bindings. It would be nice to see it with compose :)

from moko-mvvm.

Suggested modules:

• mvvm-viewmodel (viewmodel, eventdispatcher)
• mvvm-livedata (livedata, transform, state)
• mvvm-databinding (all databinding, depends on viewmodel, livedata)
• mvvm (depends on all modules)

for mvvm-viewmodel I think viewmodel should be a mandatory part of mvvm architecture at leas because the last 2 letters from mvvm means viewmodel. Also I think another dependencies(like databinding or uicompose) should be delivered separately because they have nothing in common with mvvm principles, they should act more like additional helper tools, maybe connected like plugins(like gson-converter for retrofit). That means less dependencies and less potential dependencies conflicts and frustrations on consumer projects.

from moko-mvvm.

will be released in 0.9.0

from moko-mvvm.