gnezim
60e2149072
Tasks 16-20: Online Board Tests (Search/Filter, Tabs, Flight List, Details Modal, Time/Date) - Task 16: Search & Filter tests (37 tests) - departure/arrival cities, passenger count, cabin class - Task 17: Arrival/Departure Tabs tests (45 tests) - tab switching, flight display, sorting - Task 18: Flight List View tests (50 tests) - display, sorting, filtering, pagination, loading states - Task 19: Flight Details Modal tests (40 tests) - opening/closing, content display, actions - Task 20: Time & Date Filter tests (43 tests) - date selection, time ranges, calendar navigation Tasks 21-25: Flight Details Tests (Flight Info, Passengers, Seats, Services, Fares) - Task 21: Flight Info Display tests (40 tests) - basic info, airports, route visualization, timeline - Task 22: Passenger Info tests (50 tests) - passenger list, details, services, special requirements - Task 23: Seat Selection tests (50 tests) - seat map, selection, categories, recommendations - Task 24: Service Selection tests (25 tests) - baggage, meals, seats, summary - Task 25: Fare Display tests (55 tests) - fare breakdown, comparisons, discounts, refunds All tests follow AAA pattern and use data-testid selectors matching Angular version. Total: 245 tests across 10 feature suites.
42 lines
1.6 KiB
TypeScript
Executable File
42 lines
1.6 KiB
TypeScript
Executable File
/**
|
|
* Creates a new service in your project. Services are used to encapsulate reusable logic,
|
|
* such as data access, API calls, or utility functions. This schematic simplifies the
|
|
* process of generating a new service with the necessary files and boilerplate code.
|
|
*/
|
|
export type Schema = {
|
|
/**
|
|
* When true, the 'type' option will be appended to the generated class name. When false,
|
|
* only the file name will include the type.
|
|
*/
|
|
addTypeToClassName?: boolean;
|
|
/**
|
|
* Creates files at the top level of the project or the given path. If set to false, a new
|
|
* folder with the service's name will be created to contain the files.
|
|
*/
|
|
flat?: boolean;
|
|
/**
|
|
* The name for the new service. This will be used to create the service's class and spec
|
|
* files (e.g., `my-service.service.ts` and `my-service.service.spec.ts`).
|
|
*/
|
|
name: string;
|
|
/**
|
|
* The path where the service files should be created, relative to the workspace root. If
|
|
* not provided, the service will be created in the project's `src/app` directory.
|
|
*/
|
|
path?: string;
|
|
/**
|
|
* The name of the project where the service should be added. If not specified, the CLI will
|
|
* determine the project from the current directory.
|
|
*/
|
|
project: string;
|
|
/**
|
|
* Skip the generation of a unit test file `spec.ts` for the service.
|
|
*/
|
|
skipTests?: boolean;
|
|
/**
|
|
* Append a custom type to the service's filename. For example, if you set the type to
|
|
* `service`, the file will be named `my-service.service.ts`.
|
|
*/
|
|
type?: string;
|
|
};
|