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
Case: I want to ensure my configuration is correct (no missing unmapped injections), in other words that all my dependencies tree can be successfully resolved. In my test I would get my configured injector (e.g. get actual configured context) and call verify() (for instance) on them.
I would expect injector (and it's parent injectors) to run through all mappings (Injector#_mappings) and call corresponding getInstance().
What do you think? I would be glad to implement it and make PR if I know it would be accepted.
The text was updated successfully, but these errors were encountered:
Wow! That thing would be really cool. Especially in big projects when you are waiting like FOREVER while maven is building and building and building and still building and then you are getting stupid mapping RTE.
@darscan @creynders and everyone still alive,
what do you think about some verification API?
http://stackoverflow.com/questions/9896344/ioc-container-check-for-errors-at-compile-time
Case: I want to ensure my configuration is correct (no missing unmapped injections), in other words that all my dependencies tree can be successfully resolved. In my test I would get my configured injector (e.g. get actual configured context) and call
verify()
(for instance) on them.I would expect injector (and it's parent injectors) to run through all mappings (
Injector#_mappings
) and call correspondinggetInstance()
.What do you think? I would be glad to implement it and make PR if I know it would be accepted.
The text was updated successfully, but these errors were encountered: