-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Mess Detector rules #184
Comments
That is a possibility. I am trying to cover all the bases, and hope that we get one that works. The three suggested are the ones supported by my IDE, apparently for different purposes. If a single tool would do the trick - detecing, reporting and fixing, both inside an IDE and as part of travis-ci, that would be good. From: cryode [email protected] Suggest possibly using PHP CS Fixerhttps://github.com/FriendsOfPHP/PHP-CS-Fixer to help with formatting code automatically, on top of or in lieu of mess detector. You are receiving this because you authored the thread. |
Out of curiosity, I installed Mess Detector and ran it on selected classes in my CI3 codebase. The information it provides is very different from PHP-CS. I think there's a remote possibility that you could write rules for PHP-CS to do the same thing, but it would seem like an odd thing to spend your time on, given that MD works, and you would probably take a less automated approach to dealing with MD results. |
It looks like the traction is with the code sniffer and not the mess detector. |
Looking for someone familiar with Mess Detector to create a ruleset matching our style guide, or the common deviations from it or other bad smells.
This is initially intended for use inside an IDE, and ultimately perhaps as part of our travis-ci build.
The text was updated successfully, but these errors were encountered: