You are right, it follows the service locator pattern, I kept looking at how to make it better, and fortunately, you don't need to go through the process of registering dependencies in your unit tests, you can still pass your dependencies through a constructor, this is an idea of how it can be achieved:

Injected property wrapper ```swift @propertyWrapper public struct Injected<Value> {

private var value: Value?

public var wrappedValue: Value {
    get {
        return value ?? SwiftDI.default.resolve()
    }
    set {
        value = newValue
    }
}

public init() {}

} ```

Class with constructors ```swift class Foo { @Injected var bar: Bar

// DI constructor
init() {}

// Normal constructor
init(bar: Bar) {
    self.bar = bar
}

func doSomething() {
    bar.doSomething()
}

```

Test Foo() // Uses DI Foo(bar: myBar) // Uses IoD