-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
BlocViewModel? #3
Comments
I think it should use viewmodel as you have suggested. For me the most important reason to use viewmodel is to use hilt. |
I like this suggestion - I'll look into it! |
Amazing. This will be really helpful as we will be able to use hilt, scopes and other cool stuff. Plus if google adds more features to viewmodel, we will be able to adopt them easily. Looking forward for an update. |
I have looked into the library and the it can be achieved by exteneding abstract class BlocBase<State>(initial: State) But another serious issue arises here that |
I really liked your implementation of Bloc in kotlin.
ViewModel is finely integrated with Activities (retention on activity recreate, etc) and other Android stuff in general.
Also ViewModel is responsible for holding the ui state, and reacting to ui actions (just like Bloc).
So, a
BlocViewModel
based onAndroidViewModel
/ViewModel
would be great and really useful.BlocViewModel
would be aAndroidViewModel
/ViewModel
with all capabilities ofBloc
.Your thoughts?
The text was updated successfully, but these errors were encountered: