Creating ViewModels with Mapperly

[BicycleMark]

Are there mapperly users mapping from ef core classes to ViewModels that expose public properties as INotifyPropertyChange type properties? Is that a Bad practice?

So far my research indicates that:

1. we cannot use MvvmCommunity Toolkit [ObservableProperies] on a private field - due to fact that chaining generators is not supported
2. It seems that we can Map from a Public ef core Property to a Private field on the Dto object. So I am thinking we could expose in the Dto a public property that implements the getters / setters in a traditional INotifyProoperty manner.

[latonz]

1. As you know already chaining source generators is currently not supported by .NET. See Trying to use Mapperly with the MvvmToolkit [ObservableProperty] #1445, Not mapping properties generated by other source generators #883, Mapperly do not find properties generated by [ObservableProperty] attribute #292, Working with Mapperly and MS Community Toolkit #533, FAQ and Allow for a way to ensure some source generators run before / after others dotnet/roslyn#57239.
2. You could either embed the Mapper in the DTO so that the member can safely access the private members (may break some separation principles, depending on your code architecture), or you could use private member mapping (which comes with its own limitations...).