-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(Multiple?) priority issues #3844
Comments
looks like you found some priority issue indeed (0.01666...%, glad it's not that much, still worth to fix!) Sadly, the report is so generic, that is hard to fix it out of the box. Issue deserves further investigation which pair of fixers have the priority issues |
For reference, I will of course try to nail all of them.
|
As all issues have their own issue or PR I'm closing the meta ticket here, thanks for all the work 👍 |
The PHP version you are using (
$ php -v
):PHP CS Fixer version you are using (
$ php-cs-fixer -V
):PHP CS Fixer 2.12.1 Long Journey by Fabien Potencier and Dariusz Ruminski
The command you use to run PHP CS Fixer:
vendor/bin/php-cs-fixer fix -v --using-cache=no
The configuration file you are using, if any:
Basically the same as dmvdbrugge/dynamic-components, except
explicit_string_variable
,header_comment
,no_alternative_syntax
, andno_unset_on_property
Expected behaviour
After a first successfull run, a second run should not have found things to fix.
What happens
First run fixes everything (~4.5k changed files). Second run still fixes things (75 files). Third run is clean.
Fixers applied the second run (spread over the multiple files, some in combination, others alone):
I get that this is a bit vague and will try to pinpoint some stuff, but I wanted to get this in as well, also to be able to link other issues to it.
The text was updated successfully, but these errors were encountered: