Great library design! 🚀 about di HOT 5 OPEN

I don't unit test the parts of my code using di, and I'm not a big fan of mocking either. So it has never been a problem for me. But you are not the first mentioning this, and that led to a change in the behavior of the Builder.Add method. Now it allows to redefine a service.

Once the container has been built it is not possible to alter its definitions. So if you want to mock a service, it should be done with the Builder.Add and Builder.Set methods before calling Builder.Build.

It should be possible to organize your code to make it easy to add new definitions for in your tests. With something like this for example:

// app.go
type App struct {
    Definitions []di.Def
}

func (app *App) Run() {
    builder, _ := di.NewBuilder()
    builder.Add(app.Definitions...)
    ctn := builder.Build()
    // do something with the container
}

// services/defs.go
var Definitions = []di.Def{/* the real definitions */}

// main.go
func main() {
    app := App{Definitions: services.Definitions}
    app.Run()
}

// feature_test.go
func TestFeature(t *testing.T) {
    app := App{}
    app.Definitions = append(app.Definitions, services.Definitions...)
    app.Definitions = append(app.Definitions, di.Def{/* mocked definition */})
    // test app
}

from di.

Thank you for your support !

I don't have anything new planned for the library as it already does everything that I need. But if you need a new feature or if you see a bug, don't hesitate to create an issue.

from di.

@sarulabs definitely not hesitating. The only thing I ran into is that it is a little hard to unittest when mocking is needed. If you have encountered this than I would love some suggestions.

from di.

from di.

I updated the documentation:
92a15dc

from di.