SciCatProject / SciCatProject/backend
Single repository for BE and FE
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 27
- Forks
- 37
- Avg merge
- 17h 32m
- Merged PRs (30d)
- 38
Description
Single repository for BE and FE
Summary
We are wondering porting backend and frontend in a single repository will facilitate the e2e tests and versioning.
We need to investigate more on this issue. Pros and cons.
ESS has already done it in User Office and they are happy with the outcome.
They manage to save all the commit history from the original repositoryies.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Investigate the current backend and frontend repository layouts, then review how ESS handled the User Office migration and preserved commit history. Document the pros and cons, including e2e testing and versioning, and define a clear recommendation and migration scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- full-stack, release, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100