{
"event": "PreToolUse",
"tool_name": "Bash",
"tool_input": {
"command": "\/opt\/php-tools\/vendor\/bin\/php-cs-fixer fix \/var\/www\/dev.campus.systemische-tools.de\/src\/ServiceProvider\/ChatServiceProvider.php --diff 2>&1",
"description": "Fix PHP-CS import order"
}
}
{
"tool_response": {
"stdout": "Unable to determine minimum PHP version supported by your project from composer.json: Failed to read file \"composer.json\".\nIf you need help while solving warnings, ask at https:\/\/github.com\/PHP-CS-Fixer\/PHP-CS-Fixer\/discussions\/, we will help you!\n\nPHP CS Fixer 3.92.3 Exceptional Exception by Fabien Potencier, Dariusz Ruminski and contributors.\nPHP runtime: 8.4.16\nLoaded config default.\n\n Do you want to create the config file? [yes]:\n [0] yes\n [1] no\n > PHP CS Fixer 3.92.3 Exceptional Exception by Fabien Potencier, Dariusz Ruminski and contributors.\nPHP runtime: 8.4.16\n\n [WARNING] This command is experimental \n\n ! [NOTE] While we start, we must tell you that we put our diligence to NOT \n ! change the meaning of your codebase. \n ! \n ! Yet, some of the rules are explicitly _risky_ to apply. A rule is \n ! _risky_ if it could change code behaviour, e.g. transforming `==` into\n ! `===` or removal of trailing whitespaces within multiline strings. \n ! \n ! Such rules are improving your codebase even further, yet you shall \n ! always review changes proposed by _risky_ rules carefully. \n\n Do you want to enable _risky_ rules? [no]:\n [0] yes\n [1] no\n > \n ! [NOTE] We recommend usage of `@auto` rulesets. They take insights from your \n ! existing `composer.json` to configure project the best: \n\n * `@autoPHPMigration` - Migration rules to improve code towards the minimum ``PHP`` supported by your project (taken from ``composer.json`` file).\n * `@PER-CS` - Rules that follow `PER Coding Style (https:\/\/www.php-fig.org\/per\/coding-style\/)`_, Set is an alias for the latest revision of ``PER-CS`` rules - use it if you always want to be in sync with newest ``PER-CS`` standard.\n\n Do you want to use `@auto` ruleset? [yes]:\n [0] yes\n [1] no\n > \n Do you want to use any of other recommended ruleset? (multi-choice) [none]:\n [@PhpCsFixer] Rules recommended by ``PHP CS Fixer`` team, highly opinionated. Extends ``@PER-CS`` and ``@Symfony``.\n [@Symfony ] Rules that follow the official `Symfony Coding Standards <https:\/\/symfony.com\/doc\/current\/contributing\/code\/standards.html>`_. Extends ``@PER-CS``.\n [none ] none\n > \n [OK] Configuration file created successfully as `.php-cs-fixer.dist.php`. \n\nConfig file created, re-run the command to put it in action.",
"stderr": "",
"interrupted": false,
"isImage": false
}
}