You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently the app dose follow MVVM architecture or any DI framework. Without out using the MVVM the room DB every time fetch all data whenever the activity recreate like rotating phone. If there is more data it leads to a performance issue. Implementing MVVM leads the code more maintainable.
Describe the solution you'd like
I would like to move all the data related part to the view models that is lifecycle aware component. And use Hilt for Dependency Injection.
Describe alternatives you've considered
NA
Additional context
NA
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently the app dose follow MVVM architecture or any DI framework. Without out using the MVVM the room DB every time fetch all data whenever the activity recreate like rotating phone. If there is more data it leads to a performance issue. Implementing MVVM leads the code more maintainable.
Describe the solution you'd like
I would like to move all the data related part to the view models that is lifecycle aware component. And use Hilt for Dependency Injection.
Describe alternatives you've considered
NA
Additional context
NA
Code of Conduct
The text was updated successfully, but these errors were encountered: