refactor: seperate concerns via handler, service, storage #2
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lucas/grugchat#2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
ideally, all business logic should be in a service (file chat.go) and use purely our defined go structs.
a handler would be responsible from translating incoming HTTP API request containing json into the correct Go function calls + structs.
the storage part would be responsible for translating our Go structs + functions into SQL queries.