<@U0BLRBFMM>: Thanks. I guess I was confused, is ...
# kodein
i
@salomonbrys: Thanks. I guess I was confused, is the correct pattern to create classes that take a Kodein object in the constructor and then have them resolve dependencies with it (like the first example), or that the class should take the dependencies in the constructor and be “unaware” of Kodein, but then bind a provider to that class which constructs it, supplying dependencies from Kodein?