
PHP-CS-Fixer
@PHPCSFixer
Followers
676
Following
161
Media
13
Statuses
257
Tool for automated #PHP code formatting and refactoring. π https://t.co/f5kivJM0C9
Open Source
Joined October 2022
Long-awaiting official support for #PHP 8.4 in PHP-CS-Fixer is finally here π₯³! You may find more information in release notes. Big thanks for everyone involved in this β€οΈ. Let us know if you have any problems with Fixer in your PHP 8.4 projects βΊοΈ!.
5
16
65
We're really sorry that Fixer still does not offer official support for PHP 8.4 but this is a complex task that requires a lot of time and effort - resources that all of the maintainers currently don't have. We hope to bring this support soonβ’οΈ π!.
I saw a post about Mago (`carthage-software/mago`). I support creating tools to improve things, but it's sad to hear calls for alternatives to @PHPCSFixer just because it doesn't support PHP 8.4. The community should focus on supporting package maintenance rather than replacing.
2
0
15
That's the approach we love π₯°! We're here for you, to take the chore part of coding from your shoulders, but sometimes we just need to follow our own vision, standards and conventions. What's not part of the core, always can be a custom extension π.
@_Codito_ @PHPCSFixer PHP-CS-fixer is an open-source gift that I appreciate and respect. I would never expect anything from the project other than doing exactly what they want, how they want, when they want. Nothing but love from me.
0
0
5
π’ NEW RELEASE!. Fixer v3.67 brings you new rule: `general_attribute_remove` π. With this rule you can clean up your codebase from attributes you don't need anymore. It was implemented by @RaffoTweet, which is his first contribution to our project β€οΈ.
0
3
15
Estimated date of support for this: NEVAH!! π.
Interestingly, properties with closures assigned as default value can also have property hooks, which makes the syntax a bit too curly π. Imagine default closure with actual body + hooks. oof, let's pray for @PHPCSFixer ππ.
0
0
2
We're really sorry we couldn't provide #PHP 8.4 support from day 1, but we will try to bring it as soon as possible! Any help will be truly appreciated, when it comes to both finding new failing test cases or providing fixes π. Hopefully we can make it soon!.
I've started the process of making @PHPCSFixer compatible with #PHP 8.4, at least on basic level (which means: don't break the code). Prepared changes for CI and local development environment, created a milestone and even reported first found issue π!.
0
0
13
RT @toonverwerft: Just wanted to thank the @PHPCSFixer team for the "nullable_type_declaration_for_default_null_value" rule ! #PHP84.
0
1
0
Upcoming #PHP 8.4 will be definitely great and (r)evolutionary, but it's also really demanding when it comes to providing full support in Fixer. Heck, even basic support (not failing on 8.4 syntax) may be challenging! Let us know if you're open to help us achieving this π!.
@nicolasgrekas @arnaud_lb Moreover, Asymmetric Visibility RFC was also accepted! In #PHP 8.4 it will be possible to distinguish the level of accesibility for read and write operations on class properties. It's `readonly` on steroids! Thanks @Crell and @IlijaTovilo ππ»!.
0
2
7
7οΈβ£7οΈβ£ votes about enabling parallel runner (from PR #οΈβ£7οΈβ£7οΈβ£7οΈβ£7οΈβ£) by default π
. Last word goes to @keradus anyway, but thank you all for your feedback!.
Should we enable parallel runner with CPU auto-detection by default now or should we wait until next major release? π§.
1
1
2
Another great feedback about parallel runner π! #οΈβ£7οΈβ£7οΈβ£7οΈβ£7οΈβ£.
@antv63330540 @_Codito_ @PHPCSFixer On my machine full run time went from 60 to 2.5 seconds! definitely a big improvement.
0
0
2
RT @PHPCSFixer: Should we enable parallel runner with CPU auto-detection by default now or should we wait until next major release? π§. httpβ¦.
0
2
0