❔ ViewModel normally how many classes?
In the context of MVVM are ViewModels only constituted by just one class, normally? I mean as in it being just one class that aggregates all the data from the Model that the Views may need to access...What would your general advice be in this respect?
