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
The following unit tests fail, because when you create a child injector, any provision listeners in the child modules aren't capable of listening to any provisions which can be satisfied by the parent.
This includes JIT bindings and makes it completely impossible to listen for any classes which have no-args constructors with no fields being injected.
It seems to me that a child's provision listeners should still be respected if the child injector is the one being used.
The following unit tests fail, because when you create a child injector, any provision listeners in the child modules aren't capable of listening to any provisions which can be satisfied by the parent.
This includes JIT bindings and makes it completely impossible to listen for any classes which have no-args constructors with no fields being injected.
It seems to me that a child's provision listeners should still be respected if the child injector is the one being used.
An example can be seen in the following gist:
https://gist.github.com/DarkholmeTenk/f430cf96de70b25b8fd01bc597b23abf
The text was updated successfully, but these errors were encountered: