🚀 Exciting news from the #TYPO3 community! A recent code sprint has resulted in 15 new rules for TYPO3 #Rector and introduced Fractor, a promising new tool that can handle FlexForm, TypoScript, and more. Check it out! 🌟 https://typo3.org/article/typo3-rector-on-the-move
I was asked to upgrade/update an old #laravel (5.3) project to the latest version of laravel and #php. I’ve already seen the code and let’s say it’s going to be interesting. A lot of customizations 😱 Not calling parent constructors which contain dependencies for example (probably not necessary). And also not even following certain Laravel standards. What did they use of the Laravel framework? Facades and helper functions 😑 (I really don’t like them, just use constructor DI 😉)
@rolfdenhartog if I'm correctly there is a #rector rule to transform the facades to DI. That can help you. (I found facades a bad part of the framework)
And maybe Laravel shift can help you.
Good luck upgrade!
Looking for a #rector rule to change #phpunit@test@norden.social annotation to #[Test] attribute. Could only find something for '@dataProvider' and '@testWith`. Any pointers?
@lolli if there is none to be found, make sure to create an issue in the typo3_rector github. In few weeks time, six dedicated developers meet for the sole purpose to create requested rector rules. Thanks to my employer "PIA | UDG" supporting #typo3 and #rector for the #OpenSource community we will have time and space to do so.
Am Dienstag, 12. Februar, geht es um 19 Uhr um das Thema #TYPO3 Projektübernahmen und -updates. @danielsiepmann zeigt uns, wie eine Übernahme gelingt und wie man das Projekt anschließend aktualisiert. Dabei gehts dann auch um Themen wie #CI, Linting, Testing mit @phpunit und Tools wie @phpstan oder #Rector.
Symfony configuration is one of the changes that are difficult to spot until they're removed in the next major version. Then you must Google the "invalid option id error message" and hope for a solution. That doesn't sound like an excellent way to spend your weekend, does it? Symfony actually adds a deprecation message to those...
The members of the #TYPO3 Association have selected four ideas to be funded in the first quarter of 2024. I'm particularly excited about the upcoming new #Rector rules. But also the other ideas to revive the image rendering initiative, improvements to the translation process of pages and content, and better ACLs with predefined users and groups are exciting.
If all these ideas are completed in Q1, it will be a huge step forward for TYPO3!
Hey #TYPO3 Peeps,
Ich bin nicht so der Backend / PHP Typ. Wenn ich eine EXT für PHP 7.4 habe und die aber mit PHP 8 nutzen will - kann ich dafür nicht dieses #Rector nutzen?
Klappt das?
We've had an internal linter for years, which is built on a PHP #symphony framework.
You run the linter you want and append --fix if you want it to resolve issues (if it can)
It lints things like #JS, #SCSS as well as #PHP (via #Rector and #phpstan), #Composer files and even #TYPO3 TypoScript files - all by using the open source libraries available.
It means all our developers can adhere to central linting conventions without having to update local config files.
Modernize Symfony Configs (getrector.com)
Symfony configuration is one of the changes that are difficult to spot until they're removed in the next major version. Then you must Google the "invalid option id error message" and hope for a solution. That doesn't sound like an excellent way to spend your weekend, does it? Symfony actually adds a deprecation message to those...