-
Notifications
You must be signed in to change notification settings - Fork 494
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues with the current ViewModel implementation. #40
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi Serg,
First of all, I want to thank you for the great explanation about CleanArchitecture, but I am a bit concerned about the way the ViewModel is created. Based on this approach, if a change is made in the Input, the transform function will be called and all the outputs will be recreated again. This is not necessarily right.
What if we create the ViewModel like this, in a protocol oriented way:
The ViewModel is easier to be tested and the outputs aren't recreated for every change in Input.
What do you think?
The text was updated successfully, but these errors were encountered: