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
20 lines
861 B
Plaintext
20 lines
861 B
Plaintext
import { CommandInfo } from '../command';
|
|
/**
|
|
* A command parser encapsulates a specific logic for mapping `CommandInfo` objects
|
|
* into another `CommandInfo`.
|
|
*
|
|
* A prime example is turning an abstract `npm:foo` into `npm run foo`, but it could also turn
|
|
* the prefix color of a command brighter, or maybe even prefixing each command with `time(1)`.
|
|
*/
|
|
export interface CommandParser {
|
|
/**
|
|
* Parses `commandInfo` and returns one or more `CommandInfo`s.
|
|
*
|
|
* Returning multiple `CommandInfo` is used when there are multiple possibilities of commands to
|
|
* run given the original input.
|
|
* An example of this is when the command contains a wildcard and it must be expanded into all
|
|
* viable options so that the consumer can decide which ones to run.
|
|
*/
|
|
parse(commandInfo: CommandInfo): CommandInfo | CommandInfo[];
|
|
}
|