Files
flights_web_raw/e2e/node_modules/@schematics/angular/application/schema.d.ts
T
gnezim 60e2149072 Add comprehensive e2e test suites for Tasks 16-25
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.
2026-04-05 19:25:03 +03:00

136 lines
4.8 KiB
TypeScript
Executable File

/**
* Generates a new Angular application within your workspace. This schematic sets up the
* foundational structure of your project, including the root component, module, and
* configuration files. You can customize various aspects of the application, such as
* routing, styling, and testing.
*/
export type Schema = {
/**
* The file naming convention to use for generated files. The '2025' style guide (default)
* uses a concise format (e.g., `app.ts` for the root component), while the '2016' style
* guide includes the type in the file name (e.g., `app.component.ts`). For more
* information, see the Angular Style Guide (https://angular.dev/style-guide).
*/
fileNameStyleGuide?: FileNameStyleGuide;
/**
* Include the styles for the root component directly within the `app.ts` file. Only CSS
* styles can be included inline. By default, a separate stylesheet file (e.g., `app.css`)
* is created.
*/
inlineStyle?: boolean;
/**
* Include the HTML template for the root component directly within the `app.ts` file. By
* default, a separate template file (e.g., `app.html`) is created.
*/
inlineTemplate?: boolean;
/**
* Generate a minimal project without any testing frameworks. This is intended for learning
* purposes and simple experimentation, not for production applications.
*/
minimal?: boolean;
/**
* The name for the new application. This name will be used for the project directory and
* various identifiers throughout the application's code.
*/
name: string;
/**
* A prefix to be added to the selectors of components generated within this application.
* For example, if the prefix is `my-app` and you generate a component named `my-component`,
* the selector will be `my-app-my-component`.
*/
prefix?: string;
/**
* The directory where the new application's files will be created, relative to the
* workspace root. If not specified, the application will be created in a subfolder within
* the `projects` directory, using the application's name.
*/
projectRoot?: string;
/**
* Generate an application with routing already configured. This sets up the necessary files
* and modules for managing navigation between different views in your application.
*/
routing?: boolean;
/**
* Skip the automatic installation of packages. You will need to manually install the
* dependencies later.
*/
skipInstall?: boolean;
/**
* Do not add dependencies to the `package.json` file.
*/
skipPackageJson?: boolean;
/**
* Skip the generation of a unit test files `spec.ts`.
*/
skipTests?: boolean;
/**
* Configure the application for Server-Side Rendering (SSR) and Static Site Generation
* (SSG/Prerendering).
*/
ssr?: boolean;
/**
* Create an application that utilizes the standalone API, eliminating the need for
* NgModules. This can simplify the structure of your application.
*/
standalone?: boolean;
/**
* Enable stricter bundle budget settings for the application. This helps to keep your
* application's bundle size small and improve performance. For more information, see
* https://angular.dev/tools/cli/template-typecheck#strict-mode
*/
strict?: boolean;
/**
* The type of stylesheet files to be created for components in the application.
*/
style?: Style;
/**
* The unit testing runner to use.
*/
testRunner?: TestRunner;
/**
* Sets the view encapsulation mode for the application's components. This determines how
* component styles are scoped and applied.
*/
viewEncapsulation?: ViewEncapsulation;
/**
* Generate an application that does not use `zone.js`.
*/
zoneless?: boolean;
};
/**
* The file naming convention to use for generated files. The '2025' style guide (default)
* uses a concise format (e.g., `app.ts` for the root component), while the '2016' style
* guide includes the type in the file name (e.g., `app.component.ts`). For more
* information, see the Angular Style Guide (https://angular.dev/style-guide).
*/
export declare enum FileNameStyleGuide {
The2016 = "2016",
The2025 = "2025"
}
/**
* The type of stylesheet files to be created for components in the application.
*/
export declare enum Style {
Css = "css",
Less = "less",
Sass = "sass",
Scss = "scss",
Tailwind = "tailwind"
}
/**
* The unit testing runner to use.
*/
export declare enum TestRunner {
Karma = "karma",
Vitest = "vitest"
}
/**
* Sets the view encapsulation mode for the application's components. This determines how
* component styles are scoped and applied.
*/
export declare enum ViewEncapsulation {
Emulated = "Emulated",
None = "None",
ShadowDom = "ShadowDom"
}