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
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.
The text was updated successfully, but these errors were encountered:
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
.The text was updated successfully, but these errors were encountered: