-
-
Notifications
You must be signed in to change notification settings - Fork 74
Open
Description
Very often I need to find out which service caused another service to load.
For example, I call a request where a lot of services are injected that won't be needed in the end. In a complex application, it is hard to discover the exact reason why a service was instantiated.
I suggest adding a switch to the configuration to enable path tracing of how services were instantiated, for better debug. The information could be displayed directly in the Tracy panel.
Now the path can be found out by throwing an exception, for example:
Thanks.
Metadata
Metadata
Assignees
Labels
No labels
