You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AlexanderWangY opened this issue
Apr 13, 2024
· 1 comment
Assignees
Labels
Backend📡Issues corresponding to the backend/API.MediumYou should have some familiarity with our codebase to work on this issueRefactorRewriting functions, changing names, improving code readability, reducing complexity
As of right now, our backend's endpoints are all stored in index.ts which is a monolith of code which gets pretty confusing. We'd like you to help us sort them our into separate files, one for API related functions and one for Socket related functions!
Some tips:
Use the router functionality given by expressJS and app.use it in the index.ts (possibly?)
Make initializing sockets a function that is called once in index.ts on startup?
Move other files into their respective folder's and make sure that if something breaks, we can pinpoint exactly whether it was in the sockets or api!
The text was updated successfully, but these errors were encountered:
AlexanderWangY
added
Backend📡
Issues corresponding to the backend/API.
Medium
You should have some familiarity with our codebase to work on this issue
Refactor
Rewriting functions, changing names, improving code readability, reducing complexity
labels
Apr 13, 2024
Backend📡Issues corresponding to the backend/API.MediumYou should have some familiarity with our codebase to work on this issueRefactorRewriting functions, changing names, improving code readability, reducing complexity
As of right now, our backend's endpoints are all stored in
index.ts
which is a monolith of code which gets pretty confusing. We'd like you to help us sort them our into separate files, one for API related functions and one for Socket related functions!Some tips:
app.use
it in the index.ts (possibly?)Move other files into their respective folder's and make sure that if something breaks, we can pinpoint exactly whether it was in the
sockets
orapi
!The text was updated successfully, but these errors were encountered: