aboutsummaryrefslogtreecommitdiffhomepage
path: root/README.md
diff options
context:
space:
mode:
authornsfisis <nsfisis@gmail.com>2026-08-06 02:51:52 +0900
committernsfisis <nsfisis@gmail.com>2026-08-06 02:51:52 +0900
commit27e81d5e5ca0a89eb176a65b1d9f186658b16f50 (patch)
tree3e43d18287eb1b4b64ffb7f77575de010245de79 /README.md
parent1df28c4f702045a33865d29d00ef430d8138579b (diff)
downloadphp-shirabe-27e81d5e5ca0a89eb176a65b1d9f186658b16f50.tar.gz
php-shirabe-27e81d5e5ca0a89eb176a65b1d9f186658b16f50.tar.zst
php-shirabe-27e81d5e5ca0a89eb176a65b1d9f186658b16f50.zip
test(plugin): cover composer/installers beyond a fresh install
A single install leaves the installer contract half tested: it never reaches `update`, never runs over an already-installed tree, and never reaches the plugin's own `uninstall()` override — the one chaining onto the promise `LibraryInstaller::uninstall` returns. Nor does it touch the configuration surface real projects use, `installer-paths` and `installer-name`, which the plugin reads back through the package proxy. All three now compare command output as well as the resulting tree against upstream Composer. Progress bar frames are dropped from that comparison: Shirabe renders them differently for every install, including projects with no plugin at all, so they say nothing about the plugin under test. With those covered the plugin joins the verified list in the README.
Diffstat (limited to 'README.md')
-rw-r--r--README.md1
1 files changed, 1 insertions, 0 deletions
diff --git a/README.md b/README.md
index f9f63354..736c22ee 100644
--- a/README.md
+++ b/README.md
@@ -13,6 +13,7 @@ It aims at 100% compatibility with Composer, including the plugin API.
Shirabe runs Composer plugins using the system-provided real PHP. The plugin API is partially implemented. The following plugins are verified to work:
+* [composer/installers](https://github.com/composer/installers)
* [phpstan/extension-installer](https://github.com/phpstan/extension-installer)