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.
53 lines
2.0 KiB
Markdown
53 lines
2.0 KiB
Markdown
# is-interactive
|
|
|
|
> Check if stdout or stderr is [interactive](https://unix.stackexchange.com/a/43389/7678)
|
|
|
|
It checks that the stream is [TTY](https://jameshfisher.com/2017/12/09/what-is-a-tty/), not a dumb terminal, and not running in a CI.
|
|
|
|
This can be useful to decide whether to present interactive UI or animations in the terminal.
|
|
|
|
## Install
|
|
|
|
```
|
|
$ npm install is-interactive
|
|
```
|
|
|
|
## Usage
|
|
|
|
```js
|
|
import isInteractive from 'is-interactive';
|
|
|
|
isInteractive();
|
|
//=> true
|
|
```
|
|
|
|
## API
|
|
|
|
### isInteractive(options?)
|
|
|
|
#### options
|
|
|
|
Type: `object`
|
|
|
|
##### stream
|
|
|
|
Type: [`stream.Writable`](https://nodejs.org/api/stream.html#stream_class_stream_writable)\
|
|
Default: [`process.stdout`](https://nodejs.org/api/process.html#process_process_stdout)
|
|
|
|
The stream to check.
|
|
|
|
## FAQ
|
|
|
|
#### Why are you not using [`ci-info`](https://github.com/watson/ci-info) for the CI check?
|
|
|
|
It's silly to have to detect individual CIs. They should identify themselves with the `CI` environment variable, and most do just that. A manually maintained list of detections will easily get out of date. And if a package using `ci-info` doesn't update to the latest version all the time, they will not support certain CIs. It also creates unpredictability as you might assume a CI is not supported and then suddenly it gets supported and you didn't account for that. In addition, some of the manual detections are loose and might cause false-positives which could create hard-to-debug bugs.
|
|
|
|
#### Why does this even exist? It's just a few lines.
|
|
|
|
It's not about the number of lines, but rather discoverability and documentation. A lot of people wouldn't even know they need this. Feel free to copy-paste the code if you don't want the dependency. You might also want to read [this blog post](https://blog.sindresorhus.com/small-focused-modules-9238d977a92a).
|
|
|
|
## Related
|
|
|
|
- [is-unicode-supported](https://github.com/sindresorhus/is-unicode-supported) - Detect whether the terminal supports Unicode
|
|
- [supports-color](https://github.com/chalk/supports-color) - Detect whether a terminal supports color
|