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.
51 lines
2.0 KiB
TypeScript
Executable File
51 lines
2.0 KiB
TypeScript
Executable File
/**
|
|
* Creates a new resolver in your project. Resolvers are used to pre-fetch data before a
|
|
* route is activated, ensuring that the necessary data is available before the component is
|
|
* displayed. This can improve the user experience by preventing delays and loading states.
|
|
* This schematic generates a new resolver with the specified name and options.
|
|
*/
|
|
export type Schema = {
|
|
/**
|
|
* Creates the new resolver files at the top level of the current project. If set to false,
|
|
* a new folder with the resolver's name will be created to contain the files.
|
|
*/
|
|
flat?: boolean;
|
|
/**
|
|
* Creates the resolver as a function `ResolveFn` instead of a class. Functional resolvers
|
|
* can be simpler for basic scenarios.
|
|
*/
|
|
functional?: boolean;
|
|
/**
|
|
* The name for the new resolver. This will be used to create the resolver's class and spec
|
|
* files (e.g., `my-resolver.resolver.ts` and `my-resolver.resolver.spec.ts`).
|
|
*/
|
|
name: string;
|
|
/**
|
|
* The path where the resolver files should be created, relative to the current workspace.
|
|
* If not provided, the resolver will be created in the current directory.
|
|
*/
|
|
path?: string;
|
|
/**
|
|
* The name of the project where the resolver should be created. 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 new resolver.
|
|
*/
|
|
skipTests?: boolean;
|
|
/**
|
|
* The separator character to use before the type within the generated file's name. For
|
|
* example, if you set the option to `.`, the file will be named `example.resolver.ts`.
|
|
*/
|
|
typeSeparator?: TypeSeparator;
|
|
};
|
|
/**
|
|
* The separator character to use before the type within the generated file's name. For
|
|
* example, if you set the option to `.`, the file will be named `example.resolver.ts`.
|
|
*/
|
|
export declare enum TypeSeparator {
|
|
Empty = "-",
|
|
TypeSeparator = "."
|
|
}
|