Aggrements - JU-DEV-Bootcamps/ERAS GitHub Wiki
JALA UNIVERSITY DEV-BOOTCAMP 2024-2025
For information about different technologies considered and the reasoning behind the decision made in this section, please visit Tool researchs and proposals
- Framework: Angular v19
- Component Library: Angular Material
- Charts: ???
- Framework: ASP.NET 8.0
- For ORM: Entity Framework Core
- API Testing: PostMan
- Frontend Testing: Karma
- Backend Testing: xUnit
- Container: Docker
- CI/CD: ???
- CI/CD Libraries: Husky???
- Cloud image container: Docker Hub
The Feature Branching Strategy allows developers to work on new features or bug fixes in isolated branches within submodules. This approach helps maintain a stable main branch while enabling parallel development. Steps to Implement Feature Branching in Submodules
prefix = release|feature|ci|docs|bugfix|refactor|chore|style
storyNumber = "ERAS-BE #13".specialTrim() // "BE13"
storyTitle = verb + object // "importcosmic"
${prefix}/${storyNumber}/${stroyTitle}
<NAME_IMG>:<SEM_VER>-<SHORT_SHA>-<ENV_TAG>
Being:
- <NAME_IMG>: Image name. Eg: ERAS-FE
- <SEM_VER>: Semantic version: ... Eg: 0.2.13
- <ENV_TAG>: Special tag, indicating its environment. Eg: [dev | prod]
- <SHORT_SHA>: Git's short commit SHA. Eg: 6220e0e
Examples:
- ERAS-FE:0.2.13-6220e0e-dev
- ERAS-BE:1.0.2-2342e1e-prod
- best practices for coding
- Branching strategies
- Version control strategies
- Proposed libraries
- Testing practices and minimum code coverage