title: How to build the ViewModel in MVVM not to violate the Single Responsibility Principle?
body: <p>Robert Martin says: <b>"There should never be more than one reason for a class to change"</b>.
  <br><br>Let's consider the ViewModel class which is bound to a View. It is possible (or even probable) that the ViewModel consists of properties that are not really related to each other. For small views the ViewModel may be quite coherent, but while the application gets more complex the ViewModel will expose data that will be subject to change <b> for different and unrelated reasons</b>. <br>
  <br>
  Should we worry about the SRP principle in the case of ViewModel class or not?</p>