Skip to content

DiContainer.Resolve exception handling #679

Open
@IvanMurzak

Description

@IvanMurzak

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()

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions