Roxy Light

Results 148 issues of Roxy Light

If someone wants to "override" a set of providers from a larger set, it would be helpful to have the gowire tool output the minimal code to create a new...

enhancement

### Is your feature request related to a problem? Please describe. In the past, Wire has had issues with panicing on some types of inputs. (I can't find an example...

code health
process

Wire's current installation documentation reads: > Install Wire by running: > > ```shell > go get github.com/google/go-cloud/wire/cmd/wire > ``` > > and ensuring that `$GOPATH/bin` is added to your `$PATH`....

enhancement

The [`wire.Load` function](https://github.com/google/go-cloud/blob/11bb776c80e5cc8abaa6c9aead66d5c1129c9632/wire/internal/wire/parse.go#L196), used by Wire's interactive commands, does not have any tests. While it shares much of the code with the well-tested `Generate` function, it has enough additional functionality...

blocked
code health

Other static analysis tools might want to get access to the Wire provider graph for visualization, navigation, etc. The package is currently internal so that the API can be iterated...

enhancement

Currently, Wire only considers the non-test files for injectors. To enable creation of test-only injectors, it would be nice to have Wire evaluate test files as well, creating a separate...

enhancement

(Reporting on behalf of @vangent) ### Is your feature request related to a problem? Please describe. When examining provider sets referenced in an injector, you have to rely on code...

enhancement

`golang.org/x/tools` now includes [`golang.org/x/tools/go/packages/packagestest`](https://godoc.org/golang.org/x/tools/go/packages/packagestest) — test infrastructure to set up Go workspace layouts. Using this infrastructure would allow us to remove our bespoke code to accomplish the same goal. Further,...

code health

Generated injector functions don't end up having their comments copied over from their template. It would be nice for them to preserve it.

enhancement

After [switching](https://github.com/google/go-cloud/pull/623) to using `go/packages` for analysis, the test suite for Wire (and the tool itself) has slowed on the order of 4x its previous execution times. The primary factors...

bug
blocked