Content:

Other documents:

📔 Getting Started 💡 Create components 📣 Modify component 📂 Deploy components 📝 Document component

<aside> 🚫 Changes should not be tailored to a single requirement or product, as this may cause some functionality to be lost or a product to be coupled to a specific flow.

</aside>

Generalities

Aclarations and some guidelines about the project before start to code to keeps the same code line.

Repo Location

Inside Masiv, we use Azure devops as the versioning control where all the things are upload in the **Aqua repo**

The project repository has to be allocated inside the MasivianFront azure account. The repository must be downloaded and updated from the develop branch.

Branch Naming convention

The branching name convention uses Git Flow to the creation of Branch and the management about repos must manteins a clear and obvious nomenclature.

The team that needs to modify the component must create a new branch named after the component's name, e.g.:

• For example if the component is called newFeature

  *branch name: feature/newFeature, *****

  <aside> ℹ️ In general, the branches naming should obey the following structure:

  • For corrections must be bugfix/[mainCorrection],
  • For refactor/improvement must be refactor/[mainChange],
  • For new functionalities must be feature/[mainFunctionality]. </aside>

Get Started

Step by step about how to create a component inside Aqua keeping the guidelines and order of the project.