@alessandrolai@Girgias If there is I haven't found it, yet. @Girgias suggested rule sense like where it belongs. What I meant to say is THAT RULE doesn't seem to care what order readonly comes.
🚀 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
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?
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.
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.
I've just managed to work out how to package each sperate linter into its own Docker container, so that each stage on a pipeline can run just that linter and not have to download the whole lot.
Linter configurations are odd things as I feel like I should open source it, but can't imagine anyone else would benefit as it's very niche to us