diff options
| author | nsfisis <nsfisis@gmail.com> | 2026-08-18 06:38:26 +0900 |
|---|---|---|
| committer | nsfisis <nsfisis@gmail.com> | 2026-08-18 06:38:26 +0900 |
| commit | bed0cd33ca32b95aed9d65891f97649a6f9d0069 (patch) | |
| tree | c04f9f3d6c89198222f9617f4dc84bed14fc0b4e /crates/shirabe-php-shim | |
| parent | ced1f9aa91ee36857fec9664c9ccd86ba2310821 (diff) | |
| download | php-shirabe-bed0cd33ca32b95aed9d65891f97649a6f9d0069.tar.gz php-shirabe-bed0cd33ca32b95aed9d65891f97649a6f9d0069.tar.zst php-shirabe-bed0cd33ca32b95aed9d65891f97649a6f9d0069.zip | |
fix(process-executor): model commands as a CommandLine enum
Commands were carried as `PhpMixed`, whose `String`/`List` variants do
not tell a shell command line apart from an argv list at the type level.
`Perforce::execute_command` and `Git::run_command` therefore funnelled
string commands through `execute_args`, spawning `p4 set` or
`git command` as a single argument instead of running it through a shell
as PHP does; their tests were written against that shape.
Introduce `CommandLine::{Shell, Args}` and use it for every
`ProcessExecutor` entry point, the mock expectation queue and the
`Git::run_command` callables. The unreachable "Invalid command type"
branches disappear with it, and the affected tests go back to the string
expectations the PHP suite uses.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Diffstat (limited to 'crates/shirabe-php-shim')
0 files changed, 0 insertions, 0 deletions
