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
I want to follow best practices for modern android develop and GitHub sample is a complete solution for that but there soe much old code and like using dagger 2 why its not updating to use hilt and koltin continues and flow for background work instead of executors
The text was updated successfully, but these errors were encountered:
burhankhanzada
changed the title
Why Github Smaple not updated to use hil insted of dagger 2
Why Github Smaple not updated to use hilt, coroutines and flow
Feb 17, 2021
burhankhanzada
changed the title
Why Github Smaple not updated to use hilt, coroutines and flow
Why Github Sample not updated to use hilt, coroutines and flow
Feb 17, 2021
this is so true, especially with private val viewModel: ExampleViewModel by hiltNavGraphViewModels(R.id.navgraphid) hilt nav graph parameter VM injections, I'd love to see this in sample and also an example of global actions between different nav graphs using these.
I want to follow best practices for modern android develop and GitHub sample is a complete solution for that but there soe much old code and like using dagger 2 why its not updating to use hilt and koltin continues and flow for background work instead of executors
The text was updated successfully, but these errors were encountered: