Helpline104Next

This project was generated using Angular CLI version 20.3.28.

Shared UI submodule (required after cloning)

The shared ZardUI component library lives in the Common-UI repository, wired in here as a git submodule at Common-UI/ and imported via the @common-ui/* path alias (e.g. @common-ui/ui/button). A plain git clone leaves that directory empty, so ng serve / ng build will fail to resolve @common-ui/* imports until the submodule is fetched. After cloning, run:

git submodule update --init --recursive

To pull the latest Common-UI changes from its tracked branch later, run git submodule update --remote Common-UI and commit the updated pointer.

Environment setup (required before first run)

This repo follows the AMRIT convention: the build-time environment file src/environments/environment.ts is git-ignored and generated locally. A fresh checkout has no environment.ts, so ng serve / ng build will fail until you create one. Copy the environment that matches your backend:

# Local backend services on localhost (default for development)
cp src/environments/environment.local.ts src/environments/environment.ts

The committed environment.<env>.ts files (local, dev, test, prod) are swapped in per build configuration via angular.json fileReplacements, e.g. ng build --configuration dev. The ci configuration uses environment.ci.ts, which CI generates from environment.ci.ts.template (also git-ignored) — do not create it by hand.

Development server

To start a local development server, run:

ng serve

Once the server is running, open your browser and navigate to http://localhost:4200/. The application will automatically reload whenever you modify any of the source files.

Code scaffolding

Angular CLI includes powerful code scaffolding tools. To generate a new component, run:

ng generate component component-name

For a complete list of available schematics (such as components, directives, or pipes), run:

ng generate --help

Building

To build the project run:

ng build

This will compile your project and store the build artifacts in the dist/ directory. By default, the production build optimizes your application for performance and speed.

Running unit tests

To execute unit tests with the Karma test runner, use the following command:

ng test

Running end-to-end tests

For end-to-end (e2e) testing, run:

ng e2e

Angular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.

Additional Resources

For more information on using the Angular CLI, including detailed command references, visit the Angular CLI Overview and Command Reference page.