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
I have been trying for countless hours understand why my objects weren't being created, it turns out I had marked a class on dependsOn that was being created by a registerLazySingletonAsync. Removing the dependsOn or changing the registerLazySingletonAsync to a registerSingletonAsync fixed it. So I believe registerLazySingletonAsync aren't working with the dependsOn dependency resolution, as this factory is never triggered.
The text was updated successfully, but these errors were encountered:
This should at least be documented. How could I know that some ways of registering a dependency will be a part of the dependency tree check, while others will be ignored?
I am not 100% sure that it's nothing stated. I think of you call already() you should get a warning but I can strengthen that point 8n the docs.
Am 20. Aug. 2023, 14:06 +0200 schrieb Michel Feinstein ***@***.***>:
This should at least be documented. How could I know that some ways of registering a dependency will be a part of the dependency tree check, while others will be ignored?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
Uh oh!
There was an error while loading. Please reload this page.
I have been trying for countless hours understand why my objects weren't being created, it turns out I had marked a class on
dependsOn
that was being created by aregisterLazySingletonAsync
. Removing thedependsOn
or changing theregisterLazySingletonAsync
to aregisterSingletonAsync
fixed it. So I believeregisterLazySingletonAsync
aren't working with thedependsOn
dependency resolution, as this factory is never triggered.The text was updated successfully, but these errors were encountered: