Search

This project was generated with Angular CLI version 13.3.5.

Development server

Run ng serve for a dev server. Navigate to http://localhost:4200/. The application will automatically reload if you change any of the source files.

Code scaffolding

Run ng generate component component-name to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module.

Build

Run ng build to build the project. The build artifacts will be stored in the dist/ directory.

Running unit tests

Run ng test to execute the unit tests via Karma.

Running end-to-end tests

Run ng e2e to execute the end-to-end tests via a platform of your choice. To use this command, you need to first add a package that implements end-to-end testing capabilities.

Further help

To get more help on the Angular CLI use ng help or go check out the Angular CLI Overview and Command Reference page.

Branch Names

Your branches should be named with a prefix for their purpose, viz.

• New Feature: feature-branchname
• Urgent Fix: hotfix-branchname
• Bug Fix: fix-branchname In the above examples, replace branchname with the name of your branch.

Git Commit

• chmod ug+x .husky/*
• git add CONTRIBUTING.md
• git commit   -m "docs(contributing): update contributing.md for git commit"

In general the commit pattern mostly looks like this:

• type(scope?): subject #scope is optional; multiple scopes are supported (current delimiter options: "/", "" and ",")

Common types according to commitlint-config-conventional (based on the Angular convention) can be:

• build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
• chore: Changes to the build process or auxiliary tools and libraries such as documentation generation
• ci: Changes to our CI configuration files and scripts (example scopes: Circle, BrowserStack, SauceLabs)
• docs: Documentation only changes
• feat: A new feature
• fix: A bug fix
• perf: A code change that improves performance
• refactor: A code change that neither fixes a bug nor adds a feature
• revert:Commit reverts a previous commit
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
• test: Adding missing tests or correcting existing tests