Skip to content

Commit 64b7d0d

Browse files
authored
docs: modules do not rely on models, services do (#17861)
services: provide some services for users, usually use database (models) modules: provide some basic functions without database, eg: code parser, etc The major difference is services use database, while modules don’t. Signed-off-by: singuliere <singuliere@autistici.org>
1 parent 9ecfc54 commit 64b7d0d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/content/doc/developers/guidelines-backend.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ To maintain understandable code and avoid circular dependencies it is important
3838
- `models/db`: Basic database operations. All other `models/xxx` packages should depend on this package. The `GetEngine` function should only be invoked from `models/`.
3939
- `models/fixtures`: Sample data used in unit tests and integration tests. One `yml` file means one table which will be loaded into database when beginning the tests.
4040
- `models/migrations`: Stores database migrations between versions. PRs that change a database structure **MUST** also have a migration step.
41-
- `modules`: Different modules to handle specific functionality in Gitea. Work in Progress: Some of them should be moved to `services`.
41+
- `modules`: Different modules to handle specific functionality in Gitea. Work in Progress: Some of them should be moved to `services`, in particular those that depend on models because they rely on the database.
4242
- `modules/setting`: Store all system configurations read from ini files and has been referenced by everywhere. But they should be used as function parameters when possible.
4343
- `modules/git`: Package to interactive with `Git` command line or Gogit package.
4444
- `public`: Compiled frontend files (javascript, images, css, etc.)

0 commit comments

Comments
 (0)