Repository navigation
Better collaboration and more enjoyable development #143
Description
- Design basic rules to make the project be managed well.
- Optimize the code architecture (I recommend the hexagonal architecture).
- Hold meetings to discuss features and make the requirements clear.
- Use some good development tools such as Apifox.
Activity
Hi, @BioCrossCoder . Your proposal is great. Can you propose a new project architecture? Perhaps we can discuss this matter in Discussions .
Good suggestions!
Hold meetings to discuss features and make the requirements clear.
If you have any ideas, feel free to propose them to the
Discussionand request a meeting. We can schedule the meeting together.I'm eagerly looking forward to your more detailed thoughts and plans.
And regarding the project layout, maybe we can follow this standard: https://github.com/golang-standards/project-layout
Reacted by Zhenyu LuoWell, let me study the standard on https://github.com/golang-standards/project-layout first.
I will provide a demonstration of the architecture I recommend above on this weekend.Reacted by Zike Yang and Zhenyu LuoI have just discussed with RobertIndie and we have decided not to change the current project architecture.
Just "do not add entities unless necessary".
So the 2nd term I mentioned above is already resolved.
