Nothing happend after running :CocCommand php-cs-fixer.download

[xbot]

The following command works under my project root:

./vendor/bin/php-cs-fixer fix --ansi

But nothing happend after running :CocCommand php-cs-fixer.download in vim. Files that can be formatted by the plain command cannot be formatted by this CocCommand.

[yaegassy]

Can you please run this to isolate the problem? Are you getting any error messages?

1. Run :CocCommand workspace.showOutput
2. In "Choose by number:" enter the number of php-cs-fixer
3. Run :CocCommand php-cs-fixer.fix

[xbot]

No error messages are found. The output is:

########## php-cs-fixer

Run: php vendor/bin/php-cs-fixer fix --using-cache=no --rules=@PSR12 /var/folders/px/rtcpjkg56j36pvt4ymn33r_40000gn/T/vMCguK8/tmp-236845cx81xUpi0ID
Cwd: /Users/don/my-project-root

[yaegassy]

There doesn't seem to be any problem.

coc-php-cs-fixer will use vendor/bin/php-cs-fixer if found. https://github.com/yaegassy/coc-php-cs-fixer#note

Has it been formatted?

[xbot]

No, as I said, no changes have been made to the file.

I'm not sure why the file path is a temporary one in the output above, shouldn't it be the real path? Or is that the content of the formatted temporary file will be put back to the vim buffer?

[yaegassy]

tmp file to perform the formatting and replace the results.

You have also reported an issue related to "php-cs-fixer" on coc-diagnostic, so it is probably something wrong with your environment...

---

Is the file you are trying to format a large file?

[yaegassy]

For large files, "coc.nvim" may have a timeout.

If you change this setting to a larger value, will there be any change in behavior?

  "coc.preferences.willSaveHandlerTimeout": 1000,

[xbot]

I finally found the reason. It's related to the option --rules=@PSR12.

My project has included a custom php-cs-fixer rules package by composer, I think this option conflicts with it.

I set the php-cs-fixer.rules to an empty string, it works now.

Thank you for your help.

[yaegassy]

OK, I'm glad to hear that the problem has been resolved. :)