Skip to content

Service inject initiator #278

@janbarasek

Description

@janbarasek

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:

Snímek obrazovky 2022-02-03 v 11 42 55

Thanks.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions