New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
About multiple usecases #201
Comments
I'm trying to use this template, but I'm stuck with the same damn problem. Can't seem to find a way out of this mess. |
Don't use the template, make your own code architecture for a project you building. |
You could create a "Deps" structure. Initialize it with a constructor and pass this structure to the router. ´´´ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello, I am a new to golang and clean arch!
And I am curious about the design of the usecase directory
When I start a program, the repo and the webapi part are just directly injected into the usecase and create a
translationUseCase
. Does it means that the translation usecase just representing the all usecases? But what if I want to add new usecases?If I trying to use more usecase.New in my project like
And I have to append a lot of params to
v1.NewRouter(handler, l, testUseCase)
For example:
If I do this, the NewRouter params will just grow as far as the project grow. It seem not like a good way to solve that.
Does anyone have idea about it?
The text was updated successfully, but these errors were encountered: