Invalid code generated for files ending in .class.php

[friendsofphp]

Invalid code generated for files ending in .class.php

[b-durand]

I have almost the same use case: vendor/foo.class.php for the class Foo_Service.

Psr0Fixer is more checker than a fixer IMHO. We could rename the file with the logic of the classname. The problem is to broke include instruction in others files...

[cordoval]

PSR0 demands the class name to be the same as the file name. It is also the default level or rule included when running without levels or rules by hand. If you need a warning you would first run the command with --dry-run, it is definitely the fix to rename the class according to the filename or viceversa. So it is not the fault of the tool, if you want a warning that is done in --dry-run again.
cc/ @fabpot

Please if you feel satisfied close the issue.

[keradus]

No discussion for 2 years and actually everything that can be say was said. Closing.