You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please provide minimal reproducer that don't refer to files from your filesystem. This should be a simple snippet + command like ./php-cs-fixer check --verbose --diff reproducer.php --rules='{"statement_indentation":{"stick_comment_to_next_continuous_control_statement":true}}', so it's possible to verify it without modifying local config.
Anyway, I was able to verify that \t indentation is not a problem here, since with 4-space indentation the problem is the same:
@keradus you know the most about this option, maybe you can check what happens here 🙂.
Since this issue has not had any activity within the last 90 days, I have marked it as stale.
The purpose of this action is to enforce backlog review once in a while. This is mostly for maintainers and helps with keeping repository in good condition, because stale issues and PRs can accumulate over time and make it harder for others to find relevant information. It is also possible that some changes has been made to the repo already, and issue or PR became outdated, but wasn't closed for some reason. This action helps with periodic review and closing of such stale items in automated way.
You may let maintainers handle this or verify current relevancy by yourself, to help with re-triage. Any activity will remove stale label so it won't be automatically closed at this point.
I will close it if no further activity occurs within the next 30 days.
Bug report
Description
With the attached config, the comment is not indented correctly.
Input is correct, output gets modified in a wrong way.
Runtime version
PHP CS Fixer 3.49.0 Insomnia by Fabien Potencier, Dariusz Ruminski and contributors.
PHP runtime: 8.2.7
Used command
utils/vendor/bin/php-cs-fixer fix -v --show-progress=dots --verbose -vvv
Configuration file
Referenced file :
finder.inc.php
only contains inclusion & exclusion of paths.Line in cause:
Code snippet that reproduces the problem
The text was updated successfully, but these errors were encountered: