aboutsummaryrefslogtreecommitdiffhomepage
path: root/crates/shirabe/tests/command/require_command_test.rs
diff options
context:
space:
mode:
authornsfisis <nsfisis@gmail.com>2026-08-22 17:53:13 +0900
committernsfisis <nsfisis@gmail.com>2026-08-22 17:53:13 +0900
commitec5f3292ac324789298c3a12972f8f78b688ca24 (patch)
tree44580ee521df4b0416fcafa9089695c5bc550270 /crates/shirabe/tests/command/require_command_test.rs
parent7286ee29637dbc694f769b618259eb9f75bab0fa (diff)
downloadphp-shirabe-ec5f3292ac324789298c3a12972f8f78b688ca24.tar.gz
php-shirabe-ec5f3292ac324789298c3a12972f8f78b688ca24.tar.zst
php-shirabe-ec5f3292ac324789298c3a12972f8f78b688ca24.zip
feat(cli): tell the user to run `shirabe`, not `composer`
Messages that instruct the user to run a command named the Composer binary. Shirabe ships as its own binary, so the hints now name it. File names (composer.json, composer.lock), the "composer" repository type and prose about Composer itself are untouched. The installer and functional integration fixtures live in the Composer submodule and cannot be edited, so their expected output is normalized on load.
Diffstat (limited to 'crates/shirabe/tests/command/require_command_test.rs')
-rw-r--r--crates/shirabe/tests/command/require_command_test.rs12
1 files changed, 6 insertions, 6 deletions
diff --git a/crates/shirabe/tests/command/require_command_test.rs b/crates/shirabe/tests/command/require_command_test.rs
index a4f3bb9c..897d8d2f 100644
--- a/crates/shirabe/tests/command/require_command_test.rs
+++ b/crates/shirabe/tests/command/require_command_test.rs
@@ -99,7 +99,7 @@ fn test_require_warns_if_resolved_to_feature_branch() {
assert_eq!(
"./composer.json has been updated
-Running composer update required/pkg
+Running shirabe update required/pkg
Loading composer repositories with package information
Updating dependencies
Lock file operations: 2 installs, 0 updates, 0 removals
@@ -138,7 +138,7 @@ fn provide_require() -> Vec<(
vec![("packages", InputValue::Array(vec!["required/pkg".to_string()]))],
"<warning>Cannot use required/pkg's latest version 1.2.0 as it requires ext-foobar ^1 which is missing from your platform.
./composer.json has been updated
-Running composer update required/pkg
+Running shirabe update required/pkg
Loading composer repositories with package information
Updating dependencies
Lock file operations: 1 install, 0 updates, 0 removals
@@ -165,7 +165,7 @@ Using version ^1.0 for required/pkg",
"<warning>Cannot use required/pkg's latest version 1.2.0 as it requires ext-foobar ^1 which is missing from your platform.
<warning>Cannot use required/pkg 1.1.0 as it requires ext-foobar ^1 which is missing from your platform.
./composer.json has been updated
-Running composer update required/pkg
+Running shirabe update required/pkg
Loading composer repositories with package information
Updating dependencies
Dependency resolution completed in %d seconds
@@ -190,7 +190,7 @@ Using version ^1.0 for required/pkg",
],
"<warning>Cannot use required/pkg's latest version 1.1.0 as it requires php ^20 which is not satisfied by your platform.
./composer.json has been updated
-Running composer update required/pkg
+Running shirabe update required/pkg
Loading composer repositories with package information
Updating dependencies
Lock file operations: 1 install, 0 updates, 0 removals
@@ -229,7 +229,7 @@ Using version ^1.0 for required/pkg
("--no-install", InputValue::from(true)),
],
"./composer.json has been updated
-Running composer update required/pkg
+Running shirabe update required/pkg
Loading composer repositories with package information
Updating dependencies
Lock file operations: 2 installs, 0 updates, 0 removals
@@ -251,7 +251,7 @@ Using version ^1.1 for required/pkg",
("--fixed", InputValue::from(true)),
],
"./composer.json has been updated
-Running composer update required/pkg
+Running shirabe update required/pkg
Loading composer repositories with package information
Updating dependencies
Lock file operations: 1 install, 0 updates, 0 removals