This project was generated using Angular CLI version 22.2.0.
To start a local development server, run:
ng serveOnce 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.
Angular CLI includes powerful code scaffolding tools. To generate a new component, run:
ng generate component component-nameFor a complete list of available schematics (such as components, directives, or pipes), run:
ng generate --helpTo build the project run:
ng buildThis 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.
To execute unit tests with the Vitest test runner, use the following command:
ng testFor end-to-end (e2e) testing, run:
ng e2eAngular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.
Keep work outcome-led and specifications lightweight:
- Open an issue when work needs coordination. Describe the user problem, the observable outcome, and testable acceptance criteria; include constraints or non-goals when they matter.
- Keep implementation detail in the code and tests. Update the issue or documentation when the expected behavior changes.
- Use a pull request to explain the outcome, implementation trade-offs, and verification. Keep review focused on correctness and user impact rather than ceremony or status reporting.
- Pull requests and pushes to
mainrun lint, unit tests, and a production build through the Verify workflow. Merge after those checks pass and review is complete. - Ship when the change is ready; this repository does not currently configure automated deployment.
For more information on using the Angular CLI, including detailed command references, visit the Angular CLI Overview and Command Reference page.