Jay Zhuang
Jay Zhuang
+@stytchiz who have write access
The explicit binding is there so [when multiple structs implement the same interface, wire doesn't have to guess user's intent](https://github.com/google/wire/blob/main/docs/faq.md#why-does-wire-require-explicitly-declare-that-a-type-provides-an-interface-type). The final generated code doesn't really need to reference that...
`wire.Subtract` sounds good, I'm happy to help review and merge a PR (new owner here :D)
For your needs, is it possible to consume wire as a binary? e.g. in your framework you can interact with wire through Go's `exec.Cmd`? I'd rather we don't increase the...
While I understand your need, `wire` is intended as a CLI tool, and making its library API available would make future refactors and fixes harder for `wire`. I think in...
Did you put the build constraints in `wire.go`? For example see https://github.com/google/wire/blob/9d78e0ad8cbeb6716fa6bdbca689bdb9ce0e8fe8/_tutorial/wire.go#L15-L16 If this doesn't work, can you provide a more detailed repro step? e.g. What does your source look...
Hey @xiazemin, I tried reproing your failure with the following two file, but wire ran successfully for me. Do you have a repro that I can follow? ``` ==> main.go...
`panic(wire.Build(domain_service.ProvidePRDomainService(), wire.Struct(new(ProcurementRequestServiceImpl),"*")))` should be `panic(wire.Build(domain_service.ProvidePRDomainService, wire.Struct(new(ProcurementRequestServiceImpl),"*")))` Note `domain_service.ProvidePRDomainService` should not be invoked, `wire.Build` expects a provider, not the thing returned by the provider :) @LFernandoC can you confirm if this...
If you only want to generate `wire_test.go` for a subpackage, try one of the options below: 1. Run `wire` in the directory of that subpackage 2. Run `wire gen import.path.to.subpkg`,...