Add google wire library

[dsxack]

Compile-time Dependency Injection for Go

• github.com repo: https://github.com/google/wire
• godoc.org: https://godoc.org/github.com/google/wire
• goreportcard.com: https://goreportcard.com/report/github.com/google/wire
• coverage service link: https://codecov.io/gh/google/wire

Very good coverage

Make sure that you've checked the boxes below before you submit PR:

• I have added my package in alphabetical order.
• I have an appropriate description with correct grammar.
• I know that this package was not listed before.
• I have added godoc link to the repo and to my pull request.
• I have added coverage service link to the repo and to my pull request.
• I have added goreportcard link to the repo and to my pull request.
• I have read Contribution guidelines, maintainers note and Quality standard.

Thanks for your PR, you're awesome! 👍

[avelino]

Thank you for contributing with awesome-go, we will revise your contribution as soon as possible.

Automation body content check:

• godoc.org: True
• goreportcard.com: True
• coverage: True

[panjf2000]

The code coverage is too low to meet our standard, so please increase it.

[dsxack]

@panjf2000, I'm sorry. It is google library, and I think it is too hard to increase its coverage. I think the goal does not justify the effort.

But. I start this PR only because I find in list another library with the same name wire for the same Dependency injection section.

Should I close the PR?

[panjf2000]

I appreciate your proposal but every repo in awesome-go list should be up to standard, even though it is from google.

So I'm closing this PR but still, thanks for your efforts.

[dsxack]

It is sad. The list of libraries and tools that don't contain popular libraries because of too strict standards.
And contains libraries that non-popular with the same name.
I think this will confuse new developers.
It is non-sense. Thank you.

https://github.com/Fs02/wire - has 25 stars, small documentation, runtime.
https://github.com/google/wire - has 3.2k stars, good documentation, compile-time.

Your strict standards don't do their job. Sometimes coverage 60% is much better than 100% on other library.

@panjf2000

[MihailsKuzmins]

I would also like to have the Google's wire on the list instead. It would help to get to know libraries which are used in the community most 🤔

[avelino]

Thank you for contributing with awesome-go, we will revise your contribution as soon as possible.

Automation body links content check:

• godoc.org or pkg.go.dev: True
• goreportcard.com: True
• coverage: True

your project is about to be approved, it's under revision, it may take a few days

[panjf2000]

Reopen this PR to discuss whether we should make exceptions for those repositories with more stars regardless of our standards.
@avelino

[avelino]

Reopen this PR to discuss whether we should make exceptions for those repositories with more stars regardless of our standards.

@panjf2000 was discussed in this issue #1446

in short, star is not synonym of quality

[MihailsKuzmins]

Reopen this PR to discuss whether we should make exceptions for those repositories with more stars regardless of our standards.

@panjf2000 was discussed in this issue #1446

in short, star is not synonym of quality

But is it obvious that Google's wire is used more often than the wire in the current list. In this case it would be more beneficial for developers to get to know the Google's wire. Especially taking into account that their approach is much different than that of Fx or Inject. I doubt that Google would write a library which does not comply with good practices

[avelino]

sad

@MihailsKuzmins I'm willing to talk to the package maintainers and listen to what they have to say, the communication channel via issue is open for this

[MihailsKuzmins]

@avelino thank you for not giving up 🙏
I do understand your drive to have only the best packages in the list (it's a good one, no doubt), but I simply want this package to be in the list because of its unique approach to DI (all other packages implement it with "reflect"). So I think other developers might also be interested in it (again repeating myself, sorry...)
Well, it's not that much about starts the project has