Skip to content
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.

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

DiContainer.Resolve exception handling #679

Open
IvanMurzak opened this issue Nov 1, 2020 · 0 comments
Open

DiContainer.Resolve exception handling #679

IvanMurzak opened this issue Nov 1, 2020 · 0 comments

Comments

@IvanMurzak
Copy link

When a single Zenject.DiContainer.Resolve produces an exception - all Resolve execution stops.
In my case, resolving one dependency brokes all next not yet resolved dependencies.
Could I have control over it? I want to let the resolving process to continue to resolve at least other dependencies.

P.S. I am talking about the case when on Start method Zenject resolving all dependencies. Not about manual calling Container.Resolve()

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant