The relationship of the view-model and data-model in MVVM, especially with regard to collections about reactiveviewmodel HOT 2 CLOSED

I generally like to keep model objects immutable, and put any mutable references—e.g., a changing collection—into the view model where possible. It simplifies this use case, and makes each model more like a dumb value object (a la NSString or NSDate).

When you do want/need a mutable collection in the model, ReactiveCocoa/ReactiveCocoa#1032 should make it easier to manage changes between it and the VM. Otherwise, there's no really good answer for that right now.

from reactiveviewmodel.

Thanks. Looking forward to 3.0!

from reactiveviewmodel.