Buckets:
| 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[]; | |
| } | |
Xet Storage Details
- Size:
- 861 Bytes
- Xet hash:
- 0f1661039d66540989814202ea82d220f5a58fc89b0640cf6053be43f601b8f7
·
Xet efficiently stores files, intelligently splitting them into unique chunks and accelerating uploads and downloads. More info.