<@U0Z88J25V> No, there's no way. And there won't, ...
# kodeins
salomonbrys
01/07/2019, 4:21 PM@obobo No, there's no way. And there won't, because Kodein cannot possibly call all bindings with all configurations.
o
obobo
01/07/2019, 4:22 PMI thought I had figured out a way using the onReady callback. Does this mean that onReady doesn't guarantee that the bindings will be resolvable?
s
salomonbrys
01/07/2019, 4:24 PMNo, onReady only means that it will run once all bindings have been declared in Kodein
o
obobo
01/07/2019, 4:24 PMAlso, I don't see why you'd have to call all bindings with all configurations, wouldn't it be a matter of validating the dependency graph?
s
salomonbrys
01/07/2019, 4:24 PMKodein has no such thing as a dependency graph !
salomonbrys
01/07/2019, 4:24 PMAt its core, Kodein contains lambda functions that call each other, that's all.
salomonbrys
01/07/2019, 4:26 PMWhat I could do is a way to call all bindings with no context. But that would leave all bindings that use either the context or a scope (which uses a context) out of the test...
o
obobo
01/07/2019, 4:34 PMMaybe a way to expose bindings so I can manually try and resolve them before startup? Since I know what contexts do and don't matter.
s
salomonbrys
01/07/2019, 4:35 PMWell, how are you gonna provide a fragment context for example at application start ?