EClinicFrontend

This project was generated using Angular CLI version 21.2.1.

MediFlow Frontend Structure

The app is organized by feature and role:

• src/app/core: auth store, route guard, HTTP interceptor
• src/app/shared/ui: reusable UI primitives (cards, headers, badges, forms, states)
• src/app/layout: global shell and top bar
• src/app/features/auth|patient|doctor|receptionist|admin|system
• src/app/services: typed API services for auth, appointments, slots, queue, and admin

Story Coverage Notes

• Role-based lazy routes are enforced with authGuard + route data.roles.
• Shared Tailwind/CSS utility classes in src/styles.css implement the MediFlow token system (card-surface, glass-panel, btn-primary, input-ui).
• Story verification checklist lives in src/app/features/system/story-verification-checklist.md.

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