-
Notifications
You must be signed in to change notification settings - Fork 1
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
fix: Remove fully_qualified_strict_types again #16
Conversation
Broke the update in notifications, works after bumping cs-fixer as well: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
New minor release with changelog line?
410e3c1
to
d0432bf
Compare
There are currently too many issues for the rule on the project itself #17 PHP-CS-Fixer/PHP-CS-Fixer#7719 Signed-off-by: Joas Schilling <213943+nickvergessen@users.noreply.github.com>
Signed-off-by: Joas Schilling <coding@schilljs.com>
464fe06
to
35fd40e
Compare
As per #17 we remove the rule for now again instead |
We may still want to update php-cs-fixer? |
It's not required anymore, so I prefer to not break things :-X |
Yeah but then you’re not fixing things either |
No need to fix something that is not broken. We can make a new version/branch with 2.0 requiring 8.0 and cs-fixer 3.48+ or something. |
fully_qualified_strict_types
=>leading_backslash_in_global_namespace
we want to use was only introduced with 3.46 PHP-CS-Fixer/PHP-CS-Fixer@0061223