-
Notifications
You must be signed in to change notification settings - Fork 3.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
Dependency with Dagger and android library #288
Comments
Dutch bangla bank joypurhat bangladesh. MD.ASHIKUR RAHMAN KHAN |
@apurcaroiu Uncle Bob clearly stated in this video, that you DONT want to inject anything into the Interactors (UseCase) period. Thank you. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I am working on a multi module project and I have used as a starting point this example, which helped a lot.
I am little bit stuck on this use case that I encountered:
It provides the entire billing provider integration and I decided to build it as a library as it will be referenced from other modules as well.
The issue I am struggling with is that from the payment library I need to provide to the data layer API call an instance of the data store factory. Since I already have the data store factory injected as a singleton in the app module Application Component, I am not sure if I can or should expose it to the library or I need to handle a new instance managed from within the library and not use Dagger for this specific use case and repository.
Thanks for any suggestions!
The text was updated successfully, but these errors were encountered: