lazy instantiation of objects about zenject-2019 HOT 5 CLOSED

This is how it should work. Can you explain the case in which you are seeing this?

from zenject-2019.

thinking about it, this is probably because the object is also IInitializable. Will make a test asap.

from zenject-2019.

My mistake, Zenject is effectively lazy, but the object we considered was effectively IInitializable. When removing the initialization, the object is not instantiated

from zenject-2019.

Yep, exactly. The InitializableManager has a dependency on all IInitializables and the UnityDependencyRoot has a dependency on InitializableManager so it's always created on startup.

from zenject-2019.

You might want to use [PostInject] instead which will keep it being lazily instantiated, but [PostInject] will be called in the middle of the construction of the initial object graph, so that may not be ideal.

I prefer using IInitializable for startup objects so that initialization occurs after the complete construction of the initial object graph, and also so that I can explicitly control the order that objects are initialized in, in case I need that.

from zenject-2019.