Replies: 2 comments
-
I use Wire in one of my side projects here. It's a fairly small codebase but I don't think it will change much if the codebase gets bigger |
Beta Was this translation helpful? Give feedback.
0 replies
-
I use wire for my monorepo - https://github.com/shortlink-org/shortlink/blob/main/internal/services/link/di/wire.go |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Is there an example that goes beyond 1 single file?
What's the recommended structure?
I know it all depends on the use cases and wire doesn't force users obviously.
But, I'd still like to see an example that shows how it would look in a project beyond just a single file.
What's the convention for file names and how to split them ?
I often required to create
wire.go
and multiplewire.NewSets(...)
per package, mainly because I can use in tests. For example, I've been creatingpackage_set.go
per each package that contains multiplewire.NewSets(...)
andwire.go
per package for testing.Beta Was this translation helpful? Give feedback.
All reactions