goffee/cup
1
0
Fork 2
Code Issues Pull requests 1 Projects Releases 14 Packages Wiki Activity Actions

updates

Browse source
This commit is contained in:
Zeni Kim 2024-09-16 18:36:38 -05:00
parent a756cd418d
commit 3360d106c0
2 changed files with 8 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

6
README.md
View file

@ -6,7 +6,7 @@ Cup is a skeleton project for the Goffee [Go](https://go.dev) framework made fo
## Main Features
- Routing
- Middlewares
- Hooks
- Data Validation
- Databases ORM ([GORM](https://gorm.io/) integrated)
- Emails
@ -64,8 +64,8 @@ The architecture is similar to `MVC`, where there is a routes file `./routes.go`
## The request journey:
The first component that receive's the request in `Cup` is the `Router`,
then `Goffee` locates the matching [handler](https://gocondor.github.io/docs/handlers) of the request and it check's if there are any [middlewares](https://gocondor.github.io/docs/middlewares) to be executed either before or after the [handler](https://gocondor.github.io/docs/handlers), if so, it executes them in the right order, then at the final stage it returns the response to the user.
`Request -> Router -> Optional Middlewares -> Handler -> Optional Middlewares -> Response`
then `Goffee` locates the matching [handler](https://git.smarteching.com/goffee/docs/handlers) of the request and it check's if there are any [hooks](https://git.smarteching.com/goffee/docs/hooks) to be executed either before or after the [controller](https://git.smarteching.com/goffee/controllers), if so, it executes them in the right order, then at the final stage it returns the response to the user.
`Request -> Router -> Optional Hooks -> Controller -> Optional Hooks -> Response`
## Folder structure
```bash