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.
34 lines
1.2 KiB
TypeScript
Executable File
34 lines
1.2 KiB
TypeScript
Executable File
/**
|
|
* Creates a new interface in your project. Interfaces define the structure of objects in
|
|
* TypeScript, ensuring type safety and code clarity. This schematic generates a new
|
|
* interface with the specified name and type.
|
|
*/
|
|
export type Schema = {
|
|
/**
|
|
* The name for the new interface. This will be used to create the interface file (e.g.,
|
|
* `my-interface.interface.ts`).
|
|
*/
|
|
name: string;
|
|
/**
|
|
* The path where the interface file should be created, relative to the workspace root. If
|
|
* not provided, the interface will be created in the current directory.
|
|
*/
|
|
path?: string;
|
|
/**
|
|
* A prefix to be added to the interface name. This is typically not used for interfaces, as
|
|
* they don't have selectors like components or directives.
|
|
*/
|
|
prefix?: string;
|
|
/**
|
|
* The name of the project where the interface should be created. If not specified, the CLI
|
|
* will determine the project from the current directory.
|
|
*/
|
|
project: string;
|
|
/**
|
|
* Adds a custom type to the filename, allowing you to create more descriptive interface
|
|
* names. For example, if you set the type to `data`, the filename will be
|
|
* `my-interface.data.ts`.
|
|
*/
|
|
type?: string;
|
|
};
|