-
Notifications
You must be signed in to change notification settings - Fork 113
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
PSR-1/PSR-2 #39
Comments
I don't personally know that I have a preference here. Other projects I've worked on have recently switched to PSR-2 (e.g., OpenStack-SDK-PHP). A change like this can largely be automated using PHP-CS-Fixer. @technosophos do you have any opinion? |
Also i was thinking about PHP-CS-Fixer. It is very boring have to change coding standard on IDE while switching between projects. |
My feeling is that we should stay with what is considered best practice of the community at large. My sense is that PSR-2 has the momentum now (and works with composer), so we should go that way too. The 2.x release is a great chance to make that switch at a time when users will accept it. |
PSR changes can be done when #37 is merged... |
What about change the coding standard? (With the incoming 2.0 release?)
The text was updated successfully, but these errors were encountered: