Our single page application uses 4 Github repos
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
## What is the problem?
@severinbeauvais is doing heroic work coordinating work on our single page application that is split across four Github repositories. Because each repository is responsible for a portion of the single page application there's a significant amount of code that's either duplicated or similar across the repos and it's time consuming and technically difficult to share code between repos.
## What is the impact?
* Raises the level of difficulty working on the application because each application is similar, but slightly different
* Increases time required to add new features especially when shared code is involved because shared code must be published to NPM then brought back as a required package.
* More difficult to keep interfaces and enum files in sync
* Routing between one code base to another is more complicated than it needs to be
* Code is duplicated across the repositories
## Proposed solution
Merging the repos would be time-consuming but is key to speeding up development. I'd suggest developing a detailed plan based on the following steps:
* business-filings-ui: move code from App.vue to new component, FilingsUi
* business-filings-ui: update routes.js to use full routes. For example, for the dashboard use /business/:id/ instead of just "/"
* business-edit-ui: move code from App.vue to new component, EditUi
* business-edit-ui: update routes.js to use full routes.
* business-create-ui: move code from App.vue to new component, CreateUi
* business-create-ui: update routes.js to use full routes.
* check that main.ts files are identical across all 3 "UI" repos. If not, move logic to appropriate component.
* merge routes.ts from business-edit-ui and business-filings-ui together
* merge business-edit-ui and business-filings-ui together
* if successful, merge in create-ui too
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.