Below is the guideline for Backend Development
How to set up a development environment
wire to generate dependencies.
$ go get github.com/google/wire/cmd/wire@latest
$ go generate ./...
$ go mod tidy
Or you can use
swag to generate swagger doc.
$ swag init --generalInfo ./cmd/answer/main.go
Or you can use enter the script directory and use
If this is your first time starting the Answer, it is best to compile the frontend project once to ensure that you can test it more easily. Once you get comfortable with the answer, you can copy the configuration file directly to the corresponding directory without compiling the front-end and test it with swagger.
# Frontend compilation(Recommend). If you encounter problems, please refer to the frontend related documentation
$ make ui
# enter into dir
$ cd cmd/answer/
$ go build .
If this is your first time starting the Answer, you need to follow the steps to install. If not, you can skip this step.
# init environment
$ ./answer init -C ./answer-data/
Heading to http://localhost:80/install to access installation page.
Please refer to the installation documentation for installation steps.
$ ./answer run -C ./answer-data/
Heading to http://localhost:80/ to use answer.
We use swagger to test api interface. Swagger documentation default is available. Heading to http://localhost:80/swagger/index.html to access swagger page.
You can use swagger for more convenient debugging.
├── cmd (main binary)
├── configs (default configuration)
├── docs (swagger documentation)
├── i18n (International translation)
├── base (Basic component without service attributes)
├── conf (Configuration)
├── constant (constant)
├── data (database/cache)
├── handler (request/response handler)
├── middleware (http middleware)
├── pager (Pagination)
├── reason (error reason key use to translator)
├── server (http server)
├── translator (translator for translate international)
└── validator (validator for validate request)
├── cli (binary commands)
├── controller (request handler controller for user)
├── controller_backyard (request handler controller for admin)
├── entity (all entity about database table)
├── install (installation related)
├── migrations (upgrade related)
├── repo (database/cache operations)
├── router (http router)
├── schema (request/response schema)
└── service (business logic)
├── pkg (tools or third party)
└── ui (frontend)
Dependencies between packages
For most api, the flow chart is very simple as follows.
router -> middleware -> controller(use schema) -> service -> repo(use entity)
If you want to develop a new API, you can follow the steps below.
- Adding a routing rule (GET/POST/PUT...) in router.
- Adding a controller for handler requests. the request should be validated in the controller.
- Adding a service to process business.
- Adding a repo for saving or querying data from the database or cache.
- Regenerate swagger documentation and test API.
We recommend that you follow uber's Golang Guidelines code style.
golangci-lint is a fast Go linters runner. We use golangci-lint to lint our code.
You can use the following command to check your code format.
$ go install github.com/golangci/golangci-lint/cmd/[email protected]
$ golangci-lint run
What do we need you to contribute
If you find a bug, please don't hesitate to submit an issue to us. If you can fix it, please include a note with your issue submission. If it is a bug definitely, you can submit your PR after we confirm it, which will ensure you don't do anything useless.
Code Review & Comment
In our development, some codes are not logical we know. If you find it, please don't hesitate to submit PR to us. In the same way, some function has no comment. We would appreciate it if you could help us supplement it.
Our current unit test coverage is as follows. As you can see we have many more unit tests to add, so we would be happy for you to add them.
All our translations are placed in the i18n directory.
- If you find that the corresponding key in the language you are using does not have a translation, you can submit your translation.
- If you want to submit a new language translation, please add your language to the
Features or Plugin
- We developed the features for the plan based on the roadmap. If you are suggestions for new functions, please confirm whether they have been planned.
- Plugins will be available in the future, so stay tuned.
Modify the database table structure is very hard
Usually, we don't want to modify the field that already exists in the database table. If you need to change it, follow these rules.
- Adding fields is better than modifying them.
- Modifying any field needs to take into account the impact on the existing data.
- Changes to database tables need to be tested for impact on different types of databases, and different SQL statements need to be given for different types of databases. For MySQL/PostgreSQL/sqlite3.
The Answer application's backend is built with the following components/libraries: