Is your feature request related to a problem?
The current project structure can be confusing to navigate and does not make obvious where different sets of functionality are located.
Describe the solution you'd like
We should migrate the project to a monorepo stucture with sub-packages for the UI, API, GitHub App, and Utilities. This should include breaking down files with unclear functionality into atomic files. Ex: server/repos/controller.ts splits into packages/api/repos/listMirrors.ts , packages/api/mirrors/createMirror.ts, etc.
Describe alternatives you've considered
The functionality could be split out into separate repositories instead but that would introduce additional overhead and make it harder to implement cross-component changes.
Additional context
This work should help to enable #120 since the API will be split out into it's own package that can be published separately as part of that work.
Is your feature request related to a problem?
The current project structure can be confusing to navigate and does not make obvious where different sets of functionality are located.
Describe the solution you'd like
We should migrate the project to a monorepo stucture with sub-packages for the UI, API, GitHub App, and Utilities. This should include breaking down files with unclear functionality into atomic files. Ex:
server/repos/controller.tssplits intopackages/api/repos/listMirrors.ts,packages/api/mirrors/createMirror.ts, etc.Describe alternatives you've considered
The functionality could be split out into separate repositories instead but that would introduce additional overhead and make it harder to implement cross-component changes.
Additional context
This work should help to enable #120 since the API will be split out into it's own package that can be published separately as part of that work.