DeveloperExperience: group all Composer scripts by namespace

[llaville]

Hello,

By reading the Contributing guide, I've noticed that you use the composer run-script syntax.

Even if it's always true, recent version of Composer also allows to directly run commands without run-script, I'll propose at least to group all additional commands to namespace, that will allow to discover them easily when invoking composer command without arguments (that will display help panel)

Something like :

What do you think ?

Preview on tag 4.0.1

diff --git a/composer.json b/composer.json
index 6949f5b..d461b0a 100644
--- a/composer.json
+++ b/composer.json
@@ -76,8 +76,8 @@
         }
     },
     "scripts": {
-        "cs-fix": "@php tools/php-cs-fixer/vendor/friendsofphp/php-cs-fixer/php-cs-fixer fix --diff",
-        "dev-setup": [
+        "qa:cs-fix": "@php tools/php-cs-fixer/vendor/friendsofphp/php-cs-fixer/php-cs-fixer fix --diff",
+        "qa:dev-setup": [
             "@composer -d tools/composer-normalize update",
             "@composer -d tools/composer-require-checker update",
             "@composer -d tools/composer-unused update",
@@ -86,8 +86,8 @@
             "@composer -d tools/phpunit update",
             "@composer update"
         ],
-        "normalize": "@composer -d tools/composer-normalize normalize --diff $PWD/composer.json",
-        "test": [
+        "qa:normalize": "@composer -d tools/composer-normalize normalize --diff $PWD/composer.json",
+        "test:all": [
             "@composer validate",
             "@test:psalm",
             "@test:phpunit",
@@ -103,14 +103,17 @@
         ],
         "test:composer-unused": "@php tools/composer-unused/vendor/icanhazstring/composer-unused/bin/composer-unused --excludeDir=tools",
         "test:cs-fixer": "@php tools/php-cs-fixer/vendor/friendsofphp/php-cs-fixer/php-cs-fixer fix --dry-run --diff",
-        "test:phpunit": "@php -d zend.assertions=1 -d assert.exception=1 -d display_errors=On -d error_reporting=-1 -d log_errors_max_len=0 -d memory_limit=-1 tools/phpunit/vendor/phpunit/phpunit/phpunit",
+        "test:phpunit": [
+            "@putenv XDEBUG_MODE=coverage",
+            "@php -d zend.assertions=1 -d assert.exception=1 -d display_errors=On -d error_reporting=-1 -d log_errors_max_len=0 -d memory_limit=-1 tools/phpunit/vendor/phpunit/phpunit/phpunit"
+        ],
         "test:psalm": "@php tools/psalm/vendor/vimeo/psalm/psalm"
     },
     "scripts-descriptions": {
-        "cs-fix": "Fix files according to coding standards.",
-        "dev-setup": "Install dev-requirements and tools.",
-        "normalize": "Normalize composer.json",
-        "test": "Run all tests!",
+        "qa:cs-fix": "Fix files according to coding standards.",
+        "qa:dev-setup": "Install dev-requirements and tools.",
+        "qa:normalize": "Normalize composer.json",
+        "test:all": "Run all tests!",
         "test:composer-normalize": "Test if composer.json was normalized",
         "test:composer-require-checker": "Test compoer requirements with composer-require-checker.",
         "test:composer-unused": "Test compoer requirements with composer-unused.",

[jkowalleck]

the composer run-script in the docs is there, since the docs were written in times this plugin supported composer >= v1.2
At this time, run-script was required.

It was kept, for better readability and clarity.
run-scfript will always run a script. Removing it might call native commands or plugins'induced commands. Therefore, run-scfript is intended to stay in the docs.

[llaville]

Agree with this purpose, but the goal of this discussion is grouping scripts by namespaces