SynchronizedView with TView parameters only

[Svarshick]

I have never worked with mvvm targeted frameworks. I implement mvvm in Unity and learn pattern from articles. So I might be misunderstanding the pattern. Isn't SynchronizedViewChangedEventArgs<T, TView> violates encapsulation "view doesn't know about data" in that example?

        var model = new ObservableList<SomeData>();
        var vm = model.CreateView(data => CreateView(someData)); //generates view for model data
        var view = new ScrollView(); //view has field vm
        vm.ObserveAdd().Subscribe(evt => view.Add(evt.Value.View)); //view observes vm and have acces to the evt.Value.Value (model data)

Currently, I use a View.cs file alongside .uxml to just bind uxml to the code. So I put data related logic in the vm and appearance related logic in the view (drag&drop ScrollView element). This is why view wants to look at vm.SynchronizedView, but access only TView without T. Does it make sense to create TView only SynchronizedView?

[vklubkov]

In your example, View is generated from Model. In other words, instead of Model-View-ViewModel, you only got Model-View. You even already figured this out in the comment: //generates view for model data. To make this MVVM you need to do that in two steps: first generate ViewModels from data, and then generate Views from ViewModels:

// Model layer only knows about data
var model = new ObservableList<SomeData>();

// ViewModel layer only knows about data and ViewModels
var viewModel = new ObservableList<SomeViewModel>();
var someModelView = model.CreateView(data => {
    var viewModel = CreateViewModel(someData);
    viewModel.Add(viewModel);
    return viewModel;
}); 

// View layer only knows about Views and ViewModels
var view = new ScrollView();
var someView = viewModel.CreateView(viewModel => CreateView(viewModel)); 
someView.ObserveAdd().Subscribe(evt => view.Add(evt.Value.View));

I am not that much into .uxml, so can't give any advice for it. In the classic MonoBehaviour-based MVVM you will likely have 3 classes: SomeView MonoBehaviour operating on UGUI or UITK, SomeViewModel injected into SomeVIew and e.g., SomeService in the model layer, injected into SomeViewModel.