ahmido
1fec9c6f9d
Some checks failed
Main Confidence / confidence (push) Failing after 45s
## Summary - introduce surface-aware compressed governance outcomes and reuse the shared truth/explanation seams for operator-first summaries - apply the compressed outcome hierarchy across baseline, evidence, review, review-pack, canonical review/evidence, and artifact-oriented operation-run surfaces - expand spec 214 fixtures and Pest coverage, and fix tenant-panel route assertions by generating explicit tenant-panel URLs in the affected Filament tests ## Validation - `cd apps/platform && ./vendor/bin/sail bin pint --dirty --format agent` - focused governance compression suite from `specs/214-governance-outcome-compression/quickstart.md` passed (`68` tests, `445` assertions) - `cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Feature/Filament/InventoryItemResourceTest.php tests/Feature/Filament/BackupSetUiEnforcementTest.php tests/Feature/Filament/RestoreRunUiEnforcementTest.php` passed (`18` tests, `81` assertions) Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #253
148 lines
4.1 KiB
Plaintext
148 lines
4.1 KiB
Plaintext
# Prefixing
|
|
|
|
## Prefix Styles
|
|
|
|
concurrently will by default prefix each command's outputs with a zero-based index, wrapped in square brackets:
|
|
|
|
```bash
|
|
$ concurrently 'echo Hello there' "echo 'General Kenobi!'"
|
|
[0] Hello there
|
|
[1] General Kenobi!
|
|
[0] echo Hello there exited with code 0
|
|
[1] echo 'General Kenobi!' exited with code 0
|
|
```
|
|
|
|
If you've given the commands names, they are used instead:
|
|
|
|
```bash
|
|
$ concurrently --names one,two 'echo Hello there' "echo 'General Kenobi!'"
|
|
[one] Hello there
|
|
[two] General Kenobi!
|
|
[one] echo Hello there exited with code 0
|
|
[two] echo 'General Kenobi!' exited with code 0
|
|
```
|
|
|
|
There are other prefix styles available too:
|
|
|
|
| Style | Description |
|
|
| --------- | --------------------------------- |
|
|
| `index` | Zero-based command's index |
|
|
| `name` | The command's name |
|
|
| `command` | The command's line |
|
|
| `time` | Time of output |
|
|
| `pid` | ID of the command's process (PID) |
|
|
| `none` | No prefix |
|
|
|
|
Any of these can be used by setting the `--prefix`/`-p` flag. For example:
|
|
|
|
```bash
|
|
$ concurrently --prefix pid 'echo Hello there' 'echo General Kenobi!'
|
|
[2222] Hello there
|
|
[2223] General Kenobi!
|
|
[2222] echo Hello there exited with code 0
|
|
[2223] echo 'General Kenobi!' exited with code 0
|
|
```
|
|
|
|
It's also possible to have a prefix based on a template. Any of the styles listed above can be used by wrapping it in `{}`.
|
|
Doing so will also remove the square brackets:
|
|
|
|
```bash
|
|
$ concurrently --prefix '{index}-{pid}' 'echo Hello there' 'echo General Kenobi!'
|
|
0-2222 Hello there
|
|
1-2223 General Kenobi!
|
|
0-2222 echo Hello there exited with code 0
|
|
1-2223 echo 'General Kenobi!' exited with code 0
|
|
```
|
|
|
|
## Prefix Colors
|
|
|
|
By default, there are no colors applied to concurrently prefixes, and they just use whatever the terminal's defaults are.
|
|
|
|
This can be changed by using the `--prefix-colors`/`-c` flag, which takes a comma-separated list of colors to use.<br/>
|
|
The available values are color names (e.g. `green`, `magenta`, `gray`, etc), a hex value (such as `#23de43`), or `auto`, to automatically select a color.
|
|
|
|
```bash
|
|
$ concurrently -c red,blue 'echo Hello there' 'echo General Kenobi!'
|
|
```
|
|
|
|
<details>
|
|
<summary>List of available color names</summary>
|
|
|
|
- `black`
|
|
- `blue`
|
|
- `cyan`
|
|
- `green`
|
|
- `gray`
|
|
- `magenta`
|
|
- `red`
|
|
- `white`
|
|
- `yellow`
|
|
</details>
|
|
|
|
Colors can take modifiers too. Several can be applied at once by prepending `.<modifier 1>.<modifier 2>` and so on.
|
|
|
|
```bash
|
|
$ concurrently -c red,bold.blue.dim 'echo Hello there' 'echo General Kenobi!'
|
|
```
|
|
|
|
<details>
|
|
<summary>List of available modifiers</summary>
|
|
|
|
- `reset`
|
|
- `bold`
|
|
- `dim`
|
|
- `hidden`
|
|
- `inverse`
|
|
- `italic`
|
|
- `strikethrough`
|
|
- `underline`
|
|
</details>
|
|
|
|
A background color can be set in a similarly fashion.
|
|
|
|
```bash
|
|
$ concurrently -c bgGray,red.bgBlack 'echo Hello there' 'echo General Kenobi!'
|
|
```
|
|
|
|
<details>
|
|
<summary>List of available background color names</summary>
|
|
|
|
- `bgBlack`
|
|
- `bgBlue`
|
|
- `bgCyan`
|
|
- `bgGreen`
|
|
- `bgGray`
|
|
- `bgMagenta`
|
|
- `bgRed`
|
|
- `bgWhite`
|
|
- `bgYellow`
|
|
</details>
|
|
|
|
## Prefix Length
|
|
|
|
When using the `command` prefix style, it's possible that it'll be too long.<br/>
|
|
It can be limited by setting the `--prefix-length`/`-l` flag:
|
|
|
|
```bash
|
|
$ concurrently -p command -l 10 'echo Hello there' 'echo General Kenobi!'
|
|
[echo..here] Hello there
|
|
[echo..bi!'] General Kenobi!
|
|
[echo..here] echo Hello there exited with code 0
|
|
[echo..bi!'] echo 'General Kenobi!' exited with code 0
|
|
```
|
|
|
|
It's also possible that some prefixes are too short, and you want all of them to have the same length.<br/>
|
|
This can be done by setting the `--pad-prefix` flag:
|
|
|
|
```bash
|
|
$ concurrently -n foo,barbaz --pad-prefix 'echo Hello there' 'echo General Kenobi!'
|
|
[foo ] Hello there
|
|
[foo ] echo Hello there exited with code 0
|
|
[barbaz] General Kenobi!
|
|
[barbaz] echo 'General Kenobi!' exited with code 0
|
|
```
|
|
|
|
> [!NOTE]
|
|
> If using the `pid` prefix style in combination with [`--restart-tries`](./restarting.md), the length of the PID might grow, in which case all subsequent lines will match the new length.<br/>
|
|
> This might happen, for example, if the PID was 99 and it's now 100.
|