-
Notifications
You must be signed in to change notification settings - Fork 275
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
Moving from dagger-1 to dagger-2 #597
Comments
Once this issue is resolved, we can easily start solving #540 |
After moving to Dagger 2, change the |
Switching to Hilt would be better than dagger 2 right?! |
Hilt seems to be built above Dagger 2 only. If you can go ahead and work on it, it would be nice! |
Hilt is still in alpha and we should take caution in using it in production (my opinion). What I think is first we should move to Dagger 2 then later we can add Hilt as it is based on Dagger only. |
Describe the issue
Dagger-2 has been released and we should move to it
The text was updated successfully, but these errors were encountered: