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
Will it be made into a more comprehensive framework later on? #3847
Comments
As you said, every developer has their own style of directory for their favorite projects. Will you going to make every style in one framework? Frameworks like Spring Boot and Laravel that use MVC design patterns and provide project generation. However, you need to understand MVC, and how the project configuration works. Do you need MVC and project generation whenever use gin? I prefer gin to remain simple, you can start a project with a few .go and .mod files, and it is ok. Gin doesn't give you a unified convention, but you can decide at any time. |
I also agree with what you said ,but I also believe that these features are quite good,
|
Gin has no official CLI tool, but the community makes several of them.
I think you're talking about gin-swagger |
If some codes are regularly used, you can write snippets for it. Some plugins from the editor also provide auto-complete for Go, such as Tabnine, CodeGeeX, etc... However, most of the time, I will avoid snippets and AI generation code on backend code, to prevent bugs and bad performance issues. There are many different ways to increase efficiency while writing Go, here are some tips:
example:
For example, when you handle HTTP response, you can use
|
I quite like using gin, but everyone has their own style of directory for their favorite projects. If gin can have more unified conventions and standards, and create a more powerful project framework, more people should use it
My idea:
1.Quickly generate projects
2.Unified development style
3.……
Some features of this project are worth referencing, but it encapsulates too much, link: https://github.com/gogf/gf
The text was updated successfully, but these errors were encountered: