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.
5.0 KiB
5.0 KiB
@inquirer/input
Interactive free text input component for command line interfaces. Supports validation, filtering, transformation, etc.
Installation
| npm | yarn |
|---|---|
|
|
| Or | |
|
|
Usage
import { input } from '@inquirer/prompts';
// Or
// import input from '@inquirer/input';
const answer = await input({ message: 'Enter your name' });
Options
| Property | Type | Required | Description |
|---|---|---|---|
| message | string |
yes | The question to ask |
| default | string |
no | Default value if no answer is provided; see the prefill option below for governing it's behaviour. |
| prefill | 'tab' | 'editable' |
no | Defaults to 'tab'. If set to 'tab', pressing backspace will clear the default and pressing tab will inline the value for edits; If set to 'editable', the default value will already be inlined to edit. |
| required | boolean |
no | Defaults to false. If set to true, undefined (empty) will not be accepted for this. |
| transformer | (string, { isFinal: boolean }) => string |
no | Transform/Format the raw value entered by the user. Once the prompt is completed, isFinal will be true. This function is purely visual, modify the answer in your code if needed. |
| validate | string => boolean | string | Promise<boolean | string> |
no | On submit, validate the filtered answered content. When returning a string, it'll be used as the error message displayed to the user. Note: returning a rejected promise, we'll assume a code error happened and crash. |
| pattern | RegExp |
no | Regular expression to validate the input against. If the input doesn't match the pattern, validation will fail with the error message specified in patternError. |
| patternError | string |
no | Error message to display when the input doesn't match the pattern. Defaults to 'Invalid input'. |
| theme | See Theming | no | Customize look of the prompt. |
Theming
You can theme a prompt by passing a theme object option. The theme object only need to includes the keys you wish to modify, we'll fallback on the defaults for the rest.
type Theme = {
prefix: string | { idle: string; done: string };
spinner: {
interval: number;
frames: string[];
};
style: {
answer: (text: string) => string;
message: (text: string, status: 'idle' | 'done' | 'loading') => string;
error: (text: string) => string;
defaultAnswer: (text: string) => string;
};
validationFailureMode: 'keep' | 'clear';
};
validationFailureMode defines the behavior of the prompt when the value submitted is invalid. By default, we'll keep the value allowing the user to edit it. When the theme option is set to clear, we'll remove and reset to an empty string.
License
Copyright (c) 2023 Simon Boudrias (twitter: @vaxilart)
Licensed under the MIT license.