A modern programming language that makes developers happier.

kotlinlang

Is the movement from @Model causing a bunch of rework for others? I basically have a Component Interface that has the main @Compose view() function. At construction the components get the part of the app model state they understand injected at construction time. The app model contains the whole state for the application. Right now this is a series of classes and data classes that are @Model. I think I can a similar approach by changing all the model classes to be a ton of mutableStates (seems pretty messy). Are there any restrictions on the types that can be MutableStates? @Model had limitations for arrays, lists (ModelList), and maps (ModelMap)?

Actually, `@Model` has been deprecated. It would be better to use something else instead.

I realize that model is deprecated. I am working out the best approach to migration.