Extension ignores the config setting, can't explicitly load root config

[aorcsik]

Even if I explicitly set the config settings.json, it is not passed as a command-line parameter to the executable.

I had to do a workaround by creating a wrapper script that always adds the config file sitting next to it:

settings.json

"php-cs-fixer.executablePath": "${workspaceFolder}/php-cs-fixer-wrapper.sh",

php-cs-fixer-wrapper.sh

#!/bin/bash
SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
cd "$SCRIPT_DIR"
exec "$SCRIPT_DIR/vendor/bin/php-cs-fixer" "$@" --config="$SCRIPT_DIR/.php-cs-fixer.php"

Adding the config file explicitly is a must in VSCode, since the tool runs on temp files created by the IDE and can't find config files relative to them. This caused it to switch into interactive mode, asking about risky rules, then timing out and generating .php-cs-fixer.dist.php wherever the saved file was. It was long, annoying, and didn't even fix the file. The above workaround fixed it, but fixing the issue with passing config parameters would be the real solution.

[fugikzl]

Started catching same behavior from yesterday. It ignores global rules and creates new .dist file in the directory of the target file

[arnofo]

Fixed it by creating a .php-cs-fixer.php file at the root of my project :

<?php

$finder = (new PhpCsFixer\Finder())
    ->in(__DIR__)
;

return (new PhpCsFixer\Config())
    ->setRules([
        '@PSR12' => true,
        '@Symfony' => true,
        'phpdoc_to_comment' => false,
    ])
    ->setFinder($finder)
;

(of course it has to be adapted with your own set of rules)

[axllent]

I've also noted the creation of a .php-cs-fixer.dist.php in the folder of an edited file (with a long delay) when there is no project .php-cs-fixer.php. Very annoying.

[freost]

I fixed the delay and the creation of the .php-cs-fixer.dist.php file by creating a simple proxy script that ensures php-cs-fixer runs non-interactively, and by configuring the extension to use that script as the executable.

#!/usr/bin/env bash

exec "$HOME/.config/composer/vendor/bin/php-cs-fixer" -n "$@"

[axllent]

That's great @freost , however I'm dealing with a larger team who can't be expected to configure custom scripts. In addition, we use project-installed php-cs-fixer. But thanks though, at least I know there is a workaround.