Uh oh!
There was an error while loading. Please reload this page.
Enable binary_operator_spaces - #1
Conversation
Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
nickvergessen
commented
Oct 5, 2020
So how do we do things like this? always bump the major? |
ChristophWurst
commented
Oct 5, 2020
Excellent question. I'm not sure. Breaking change would mean that the API the lib exposes changes, right? And then it becomes a bit unclear if a change like this is a breaking one or not. Yes, the code needs to be formatted differently, but we use the lib the same way. Other linting libs like https://github.com/vuejs/eslint-plugin-vue/releases have a sane SEMVER but they expose just the rules. We enforce all of them by default. I think I'll just try to get a set of changes in and then do a major bump. But I'm not sure how to handle individual changes like this one if this was to be released ASAP. |
Docs at https://github.com/FriendsOfPhp/PHP-CS-Fixer.
This is also used by Symfony.
I like it because it gives consistency.
Demo: nextcloud/server#23189