Guidance on Two-Way Binding on a Model property

[klemmchr]

Guidance on Two-Way Binding on a Model property

[SSchulze1989]

Thank you very much for the quick response and the change.
Exactly what i needed and working like a charm!

[SSchulze1989]

To elaborate, i was looking for something less verbose than:

public string Name
    {
        get => _model.Name;
        set
        {
            _model.Name = value;
            OnPropertyChanged(nameof(Name));
        }
    }

On top of that, could the

[CallerMemberName]

attribute also be added to OnPropertyChanged Method, so i can at least just write

OnPropertyChanged()

?

[klemmchr]

Currently there is no built-in solution for this. Could you elaborate why you want a binding on a sub model? Is the model changed externally outside of the view model?

[SSchulze1989]

The Model is part of my Business Logic that communicates with a REST Api. The ViewModel should enable modifying the Model and then sending a request back to the Api without having to map in between the models.

[klemmchr]

This could only be achieved by having a binding on a type that implements INotifyPropertyChanged and then listen to changed events on this end. Would be a new feature and possibly be a bit tedious to implement because it would break with current behavior. Would that suit you?

[SSchulze1989]

Ah I think i did not get that across correctly.
I do not want the Model to notify on the ViewModel. The ViewModel would still invoke the notification itself but the changes should be reflected on the Model so that the Business logic can handle the requests.

So I want the Model to hold the state for the api client and the ViewModel for interaction with the component.
I updated my code example a little so maybe it gets clearer.
In the end I think I can do with what I have shown in the example if there is not a build in way to deal with it.

Would it still be possible to add [CallerMemberName] to the OnPropertyChanged() Method?