-
Notifications
You must be signed in to change notification settings - Fork 112
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
Improve php-cs-fixer setup #185
Conversation
Hey @yariksheptykin thank you for your contribution. Unfortunately we cannot accept it. The CS-Fixer rules are a company managed topic. Changing those rules needs to be considered for every bundle. In such cases it is always better to open up a issue/discussion first, so we can evaluate the situation and give you feedback beforehand. |
Hey @mattamon ! I don't understand what you mean. Do you mean that you at pimcore want to have a uniform cs-fixer ruleset that applies to all bundles and the skeleton? And you suggest to open issue first to duscuss which rules should go into the ruleset? To clarify: my vision for this PR was to make use of the file that is already being shipped with the skeleton. I wanted to make sure that this file stays up to date, therefore I added cs-lint to CI. I also wanted to fix cs for the sources we ship with the skeleton. Whoever creates a new pimcore project from the skeleton should be able to quickly set up cs fixer, and the first commit should not be: "fixing cs in skeleton sources". |
@yariksheptykin Okay thank you! I will close your PR and merge mine. It would be awesome if you could open up a discussion! https://github.com/orgs/pimcore/discussions |
This PR: