8000 When a service fails to resolve, provide the full path to the location. · Issue #155 · Keboo/AutoDI · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

When a service fails to resolve, provide the full path to the location. #155

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
KennethWhite opened this issue Jun 18, 2019 · 2 comments
Open

When a service fails to resolve, provide the full path to the location. #155

KennethWhite opened this issue Jun 18, 2019 · 2 comments
Labels
enhancement

Comments

@KennethWhite
Copy link
Contributor

Currently you can register a delegate to fire when AutoDI fails to resolve a service type. It would be useful if in addition to reporting the type that failed to resolve it also gave the location where the attempted dependency resolution occurs.
@Keboo Keboo added this to the 4.0.2 milestone Sep 14, 2019
@Keboo
Copy link
Owner
Keboo commented Sep 14, 2019

@KennethWhite do you recall when "gave the location" means? Was looking at implementing this but can't recall the specifics of the issue we ran into.

@Keboo Keboo removed this from the 4.0.2 milestone Sep 14, 2019
@KennethWhite
Copy link
Contributor Author

@KennethWhite do you recall when "gave the location" means? Was looking at implementing this but can't recall the specifics of the issue we ran into.

It was an issue where a particular object could not be constructed but the stack track doesnt include the location of the CTOR to see what dependency isnt registered if I recall correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Keboo @KennethWhite
0