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.
48 lines
1.7 KiB
TypeScript
48 lines
1.7 KiB
TypeScript
/// <reference types="node" />
|
|
import { signals } from './signals.js';
|
|
export { signals };
|
|
/**
|
|
* A function that takes an exit code and signal as arguments
|
|
*
|
|
* In the case of signal exits *only*, a return value of true
|
|
* will indicate that the signal is being handled, and we should
|
|
* not synthetically exit with the signal we received. Regardless
|
|
* of the handler return value, the handler is unloaded when an
|
|
* otherwise fatal signal is received, so you get exactly 1 shot
|
|
* at it, unless you add another onExit handler at that point.
|
|
*
|
|
* In the case of numeric code exits, we may already have committed
|
|
* to exiting the process, for example via a fatal exception or
|
|
* unhandled promise rejection, so it is impossible to stop safely.
|
|
*/
|
|
export type Handler = (code: number | null | undefined, signal: NodeJS.Signals | null) => true | void;
|
|
export declare const
|
|
/**
|
|
* Called when the process is exiting, whether via signal, explicit
|
|
* exit, or running out of stuff to do.
|
|
*
|
|
* If the global process object is not suitable for instrumentation,
|
|
* then this will be a no-op.
|
|
*
|
|
* Returns a function that may be used to unload signal-exit.
|
|
*/
|
|
onExit: (cb: Handler, opts?: {
|
|
alwaysLast?: boolean | undefined;
|
|
} | undefined) => () => void,
|
|
/**
|
|
* Load the listeners. Likely you never need to call this, unless
|
|
* doing a rather deep integration with signal-exit functionality.
|
|
* Mostly exposed for the benefit of testing.
|
|
*
|
|
* @internal
|
|
*/
|
|
load: () => void,
|
|
/**
|
|
* Unload the listeners. Likely you never need to call this, unless
|
|
* doing a rather deep integration with signal-exit functionality.
|
|
* Mostly exposed for the benefit of testing.
|
|
*
|
|
* @internal
|
|
*/
|
|
unload: () => void;
|
|
//# sourceMappingURL=index.d.ts.map
|