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
This will clash in a project with both Anvil and Dagger modules, as in one dependency graph () -> MyThing can either be provided with or without wildcards, but not both.
Yep, that works – It's a bit of an issue for us to fix this in a rather large codebase 😅 But as far as I understand, changing this in Anvil would be a breaking change, so I'm not 100% clear on what the solution could be.
Given:
Anvil will generate this factory:
Translated to Java, the type of
Provider<@JvmSuppressWildcards () -> MyThing>
isProvider<Function0<MyThing>>
.If we would let Dagger generate the factory, it would look like this:
This will clash in a project with both Anvil and Dagger modules, as in one dependency graph
() -> MyThing
can either be provided with or without wildcards, but not both.Sample project
https://github.com/hannesstruss/anvil-wildcards
The text was updated successfully, but these errors were encountered: