Uh oh!
There was an error while loading. Please reload this page.
fix: Remove fully_qualified_strict_types again - #16
Conversation
nickvergessen
commented
Feb 1, 2024
Broke the update in notifications, works after bumping cs-fixer as well: |
come-nc
left a comment
There was a problem hiding this comment.
New minor release with changelog line?
Uh oh!
There was an error while loading. Please reload this page.
410e3c1 to
d0432bfCompareThere are currently too many issues for the rule on the project itself #17PHP-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
35fd40eComparenickvergessen
commented
Feb 1, 2024
As per #17 we remove the rule for now again instead |
come-nc
commented
Feb 1, 2024
We may still want to update php-cs-fixer? |
nickvergessen
commented
Feb 1, 2024
It's not required anymore, so I prefer to not break things :-X |
come-nc
commented
Feb 1, 2024
Yeah but then you’re not fixing things either |
nickvergessen
commented
Feb 1, 2024
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_namespacewe want to use was only introduced with 3.46 PHP-CS-Fixer/PHP-CS-Fixer@0061223