[Epic]: Monorepo

[Andreasgdp]

Priority

MAJOR

Description

As a developer, I would like to have the complete codebase for MealPlanr in one repo to simplify additions, builds, tests etc.

• Setup NX for monorepo #2
• Move MealPlanr to monorepo #3
• Move MealPlanr-api to monorepo #4
• Investigate if other repos should be added as well
  • No other issues for now
• Move all workflows to monorepo and make them work for specific applications #5
• Setup easy to use issue workflows #6
• Create projects specific for each application as well as an overall project for the complete monorepo #7

UX

No UX

Acceptance criteria

• The API needs to be moved to this repo
• All issues and information from the API needs to moved and/or merged into this repo

Comments / questions

No response

Definition of ready/done (DOR/DOD) [DONT CHANGE THE CONTENT]

Definition of ready

• DOR

  Description

  - Acceptance criteria written and reviewed by QA, PM and SE
  - Behaviour scenarios written
  - Signed off UX
  - Estimated and appropriately scoped
  

Definition of done

• DOD

  Description

  - Test complete
      - Merged to master
      - Unit tests on all new code (80% coverage)
      - Integration tests for endpoints / web sockets
      - End-to-end or integration tests verifying acceptance criteria
  - Code complete
      - Peer reviewed (1 person/people)
      - Follows BHelpful code standards / versioning guidelines
      - No commented out code or TODOs
      - TSLint / Sonarqube exceptions have explicit explanations
  - Verified by QA
      - Functionally manually verified on a setup like the actual setup
      - QA verifies test coverage aligns with master test plan
  - Verified by UX and product owner / verified by the team
  - Documentation of tech debt
  - Persistent technical documentation updated / written
      - Ready is updated / written
  

Code of Conduct

• I agree to follow this project's Code of Conduct

[Andreasgdp]

https://youtu.be/1eHlaVoeDfU

[Andreasgdp]

https://youtu.be/9iU_IE6vnJ8

[Andreasgdp]

https://stackoverflow.com/questions/58136102/deploy-individual-services-from-a-monorepo-using-github-actions

[Andreasgdp]

The MonoRepo could be a completely new repo, that is a monorepo of all the apps that some way or another would benefit from having easy access to all the tools created in such a generalised repo containing all the apps that in some way or another talk to each other.

If this is the case, development on the current repos, should just continue until the setup of the MonoRepo is ready, so we can move the development there.

For repos, that won't benefit from the movement to the large MonoRepo, will still just be individual repos (like smaller independent applications and scripts).

[Andreasgdp]

This issue should be moved to
https://github.com/BHelpful/BHelpful
If we choose to create a big complete monorepo

[Andreasgdp]

We should have a discussion on the idea of open source for all the projects in the MonoRepo, since we would need to do this for all the applications in there.

[Andreasgdp]

https://youtu.be/VUyBY72mwrQ