Skip to content
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

Support Hilt and @InstallIn #224

Open
RBusarow opened this issue Oct 17, 2021 · 0 comments
Open

Support Hilt and @InstallIn #224

RBusarow opened this issue Oct 17, 2021 · 0 comments
Labels
feature New feature or request

Comments

@RBusarow
Copy link
Member

Similar to Anvil, but different.

Anything with an @AndroidEntryPoint or @InstallIn(...) annotation must be visible to the Hilt application's module, so those dependencies should probably be "used".

But just like with #223, that just means that the dependency is needed in order to create a binding. But if that binding isn't actually used, then the dependency can be dropped.

For instance, if :libF has a fragment with @AndroidEntryPoint (and nothing else), but nothing actually navigates to that fragment, then :app should not depend upon :libF.

@RBusarow RBusarow added the feature New feature or request label Oct 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant