Skip to content
This repository has been archived by the owner on Jul 18, 2023. It is now read-only.

Decouple all of the different go files into the correct packages #181

Open
logan-hendricks opened this issue Aug 3, 2020 · 2 comments
Open
Assignees

Comments

@logan-hendricks
Copy link
Collaborator

We have been building almost all of server using the main package. This likely should not be the case. While there are a couple of different ways we could break up the packages. I currently propose the following.

  • service
    • uno.go
    • deckUtils.go
  • route
    • routeHandlers.go
    • jwt.go

This issue is entirely up for debate and review from the team. If others have different opinions on how this should be structures. Speak now or forever hold your peace

@hhenrichsen
Copy link
Collaborator

I'd call the second package api instead, I think that more fully encompasses jwt.go.

@logan-hendricks
Copy link
Collaborator Author

I can second api that makes sense to me.

@hhenrichsen hhenrichsen self-assigned this Aug 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants