-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Look into replacing MvxViewModel and derivatives #4438
Comments
Cheesebaron
changed the title
Look into replacing MvxViewModels and derivatives with CommunityToolkit
Look into replacing MvxViewModel and derivatives
Jul 14, 2022
Instead of replacing, it could be an addition. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I would love to do composition over inheritance for anything MVVM related, such that consumers of MvvmCross can choose to use their own implementation of INotifyPropertyChanged, use CommunityToolkit or perhaps ReactiveUI or whatever they feel like.
Instead of being forced to inherit from MvxViewModel or similar, just because it contains some lifecycle methods that are convenient.
To receive the lifecycle callbacks, could also be a composition detail, such as inheriting from a IMvxViewModelLifecycle interface.
The text was updated successfully, but these errors were encountered: