Other documents:

📔 Getting Started 👷🏻 In deep 💡 Create components 📣 Modify component 📝 Document component

Before all

Firts of all, the developer needs to considerer that the current branch meets the requirements of the branch appointment:

For example if the changes are about the adding a variant of a TextField

feature/add-[nameOfTheVariant]-text-field

<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>

Once that's done, it’s recommended create a test package and install this in some project to test the component Behavior in a external enviroment. To do that, firts once the developer needs run the next commands:

It’s recommended test the functionality in the local files, so create a test version

• npm version 0.0.[number-of-test-version]: → Change the version of the project
• npm run build-bundle → Create the project bundle
• npm run pack → Compile the project in a local package (This step only it’s necessary if you want test directly with the package)
• npm publish → Publish the Aqua version in the artifacts, this allow the posibility to install the project with the version that the developer set in the first step
  • If the npm version is 0.0.60, you can install this version with npm i @masiv/[email protected]

If the developer test local and externally the project and in both cases all the components are workin correctly and the new change is done, that meanings that all is check. so it can now be deployed

When all this steps are done, the behavior are correctly working and the changes are done, create a PR of the current Branch from Dev.

PR Guidelines

• Response times to a PR will be 2 - 8 working hours.
• The branches naming should obey the established structure: