wire
wire copied to clipboard
google
Compile-time Dependency Injection for Go
Fixes #411 Go 1.23.0 has several new features, which have no direct bearing on wire's ability to reflect, but, which disallow using a binary built with an older go from...
Change text of the expected error to fix the current test failer of TestWire/UnexportedStruct. Fix #412.
### Describe the bug `go test ./...` fails with `go1.23.0` and `go1.22.6` due to a minor change in the error wording: ```bash $ go test ./... ? github.com/google/wire [no test...
## Changes - Replaced all deprecated `ioutil` functions with their `io` or `os` equivalents (supported since Go 1.16+). - Removed unused `io/ioutil` imports. - Verified that tests pass (`go test...
### Describe the bug When running wire gen on our project, the Wire process experiences uncontrolled memory growth (exceeding 80GB), eventually triggering OOM termination. This occurs during dependency graph analysis/code...
# Summary This PR refines the naming of cleanup functions in generated code to enhance clarity and correctness. Previously, Wire generated cleanup functions with generic names (`cleanup`, `cleanup2`), which made...
### What version of Go are you using (`go version`)? $ go version go version go1.24rc2 darwin/arm64 ### Does this issue reproduce with the latest release? I am running the...
### Describe the bug ProviderSet like : ``` import ( "dependence-project/s3" "dependence-project/s3/minio" "github.com/google/wire" ) var ProviderSet = wire.NewSet(NewS3) func NewS3(dataConf *conf.Data) (s3.S3, error) { return minio.NewS3(dataConf.Minio.Endpoint, dataConf.Minio.AccessKeyId, dataConf.Minio.SecretAccessKey, false, "")...
adding "name" because runtests.sh reports: ``` wire_test.go:121: Errors didn't match expected errors from wire_errors.txt: {[]string}[0]: -: "example.com/foo/wire.go:x:y: name foo not exported by package bar" +: "example.com/foo/wire.go:x:y: foo not exported by...
