#phpcompatibility search results

Just to be clear - this is not intended as criticism of the Docs team, who do amazing work! Just a returning frustration of PHP moving faster than the docs can keep up and the amount of extra work this causes to maintain #PHPCompatibility. Either way - result:

jrf_nl's tweet image. Just to be clear - this is not intended as criticism of the Docs team, who do amazing work!

Just a returning frustration of PHP moving faster than the docs can keep up and the amount of extra work this causes to maintain #PHPCompatibility.

Either way - result:

Current status: doing my annual round of updating the (always incomplete) #PHP (8.1) Migration Guide based on the research I did to create the PRs for #PHPCompatibility ... *sigh*



2/7 🎯 Divi Booster maintient une compatibilité avec différentes versions de PHP en effectuant des tests réguliers avec la dernière version de la bibliothèque phpcompatibility code sniffer. Un travail technique rigoureux pour une meilleure performance. #PHPCompatibility


12 years ago today I published the first version of PHP53Compat_CodeSniffer on Github, which later turned into PHPCompatibility. 12 years later @jrf_nl is running the show and the project is being used by tens of thousands of projects. Open source works ! #phpCompatibility


Been a while since I had time to work on #PHPCompatibility, but I just wrote a new sniff to detect for one of the #PHP 8.1 deprecations. #MakingThingsBetter


5/7 🔒 Avant d'exécuter le PHP Compatibility Checker, il est recommandé de désactiver Divi Booster. Divi Booster utilise la dernière version de la bibliothèque de compatibilité PHP pour ses tests internes. #Simplicity #PHPCompatibility


Quão compatível é o seu código PHP e sua loja Magento? Será que ele funciona em todas as versões do PHP? Descubra com um comando. ow.ly/FbwE50BuauE #PHP #Magento #PHPCompatibility #betterCoding

magenteiro's tweet image. Quão compatível é o seu código PHP e sua loja Magento? Será que ele funciona em todas as versões do PHP? 
Descubra com um comando. 
ow.ly/FbwE50BuauE 
#PHP #Magento #PHPCompatibility #betterCoding

@adamculp do you know if PHPCompatibility checks for parameter mismatch in functions and methods #phpuk19 #PHPCompatibility #phpupgrade


And then there were four... (new #PHPCompatibility sniffs). Oops.. I seem to be on a roll... github.com/PHPCompatibili…

Been a while since I had time to work on #PHPCompatibility, but I just wrote a new sniff to detect for one of the #PHP 8.1 deprecations. #MakingThingsBetter



Yet another PHP 8.0 compatibility sniff done. Thanks @elazar for contributing! #php8 #phpcompatibility github.com/PHPCompatibili…


This just in: #PHPCompatibility 9.3.2 has been released containing a few essential bugfixes, along with PHPCompatibilityParagonie 1.2.0 which is an update for full compatibility with #sodium_compat 1.11.0. #php Enjoy! github.com/PHPCompatibili… github.com/PHPCompatibili…


For all #PHPCompatibility users out there currently using the `develop` branch: PHPCSUtils-1.0.0alpha4 has been released, so make sure you use `composer update --with-[all-]dependencies` when updating PHPCompatibility!


Lots of new developments on PHPCompatibility coming up, after a very productive face-to-face meeting @jrf_nl yesterday :-) #phpcompatibility


Tester la compatibilité de son code avec les anciennes versions de #PHP acseo-conseil.fr/tester-la-comp… #codesniffer #PHPCompatibility #pear


I wanted to try it out, but unfortunately this package does not support #PHPCompatibility 10.x-dev which I used for our #PHP 8.2 runtime. So I'll stick with ignore rules for now 🙂


PHPCompatibility standard for PHP 7.1 was just released. Get it through composer or Github : github.com/wimg/PHPCompat… #php #phpcompatibility


Productive weekend... Got commits lined up to be pulled to #PHPCompatibility covering about 50% of the #PHP 8.1 changes via RFCs. No doubt there will be still way more to account for based on the changelogs etc, but I'd call this a great start. #MakingThingsBetter


PHPCompatibility 8.2.0 was just released, with tons of new additions, changes and some fixes. It also prepares for 9.0.0 which will have major restructuring and some breaking changes. You can find it under its own organization now : github.com/PHPCompatibili… #PHPCompatibility #php


After the merge, we will utilise #PHP 8.3 in all our Docker-based instances, and gradually migrate older infrastructure. When everything is ready, we will change constraint in `composer.json`, #PHPCompatibility config and shared .idea setup (#PHPStorm), and unlock 8.3 fully 😁.


Traditionally, tools that helped us a lot were: - @phpstan that checks if our code uses PHP built-ins properly - @PHP_CodeSniffer with #PHPCompatibility ruleset that ensures our code is compatible with 8.2-8.3 - #PHPUnit that runs our tests (unit and integration)


Learn how to test your #WordPress plugins for PHP compatibility and ensure that your site is running smoothly. This article covers everything from what PHP is to how to manually test your plugins and use the #PHPCompatibility tool to automate the process. learn.wordpress.org/tutorial/testi…


5/7 🔒 Avant d'exécuter le PHP Compatibility Checker, il est recommandé de désactiver Divi Booster. Divi Booster utilise la dernière version de la bibliothèque de compatibilité PHP pour ses tests internes. #Simplicity #PHPCompatibility


2/7 🎯 Divi Booster maintient une compatibilité avec différentes versions de PHP en effectuant des tests réguliers avec la dernière version de la bibliothèque phpcompatibility code sniffer. Un travail technique rigoureux pour une meilleure performance. #PHPCompatibility


Don't forget that we have excellent tooling in #PHP ecosystem! You're not alone with your upgrades, you can use @PHPCSFixer, @rectorphp, #PHPCodeSniffer with #PHPCompatibility plugin and probably many other tools. Trust me, it's doable 😁.


I wanted to try it out, but unfortunately this package does not support #PHPCompatibility 10.x-dev which I used for our #PHP 8.2 runtime. So I'll stick with ignore rules for now 🙂


I've analysed our codebase with #PHPCompatibility against 7.4-8.2 range using 10.x-dev version, and it found 97 errors, so let's take a look at them 🙂. Some of them are false-positives, but the other ones will allow to actually fix potential problems! #PHP thread 🧵👇

Please make sure you use the `develop` branch for PHP 8.x issue detection (at least until PHPCompatibility 10.0 has been released). Secondly, no, detection is not complete. Some things still need to be added, some things cannot be detected via this type of static analysis.



I asked because we fixed already almost every problem in our CI for PHP8.2 runtime, and in terms of #PHPCompatibility it has been reporting mostly warnings (that we decided to hide and don't focus on them). So it was a little suspicious 😉. I'll try develop branch today.


I'm reviewing #PHP's incompatible changes in 8.0-8.2, wondering if #PHPCompatibility ruleset covers them all? @wimgtr @jrf_nl could you provide some info? 🙂 We have it implemented in CI both for 7.4 (current) and 8.2 (separate branch), I would like to be sure it's enough.


For all #PHPCompatibility users out there currently using the `develop` branch: PHPCSUtils-1.0.0alpha4 has been released, so make sure you use `composer update --with-[all-]dependencies` when updating PHPCompatibility!


12 years ago today I published the first version of PHP53Compat_CodeSniffer on Github, which later turned into PHPCompatibility. 12 years later @jrf_nl is running the show and the project is being used by tens of thousands of projects. Open source works ! #phpCompatibility


Just to be clear - this is not intended as criticism of the Docs team, who do amazing work! Just a returning frustration of PHP moving faster than the docs can keep up and the amount of extra work this causes to maintain #PHPCompatibility. Either way - result:

jrf_nl's tweet image. Just to be clear - this is not intended as criticism of the Docs team, who do amazing work!

Just a returning frustration of PHP moving faster than the docs can keep up and the amount of extra work this causes to maintain #PHPCompatibility.

Either way - result:

Current status: doing my annual round of updating the (always incomplete) #PHP (8.1) Migration Guide based on the research I did to create the PRs for #PHPCompatibility ... *sigh*



Current status: doing my annual round of updating the (always incomplete) #PHP (8.1) Migration Guide based on the research I did to create the PRs for #PHPCompatibility ... *sigh*


Productive weekend... Got commits lined up to be pulled to #PHPCompatibility covering about 50% of the #PHP 8.1 changes via RFCs. No doubt there will be still way more to account for based on the changelogs etc, but I'd call this a great start. #MakingThingsBetter


And then there were four... (new #PHPCompatibility sniffs). Oops.. I seem to be on a roll... github.com/PHPCompatibili…

Been a while since I had time to work on #PHPCompatibility, but I just wrote a new sniff to detect for one of the #PHP 8.1 deprecations. #MakingThingsBetter



Been a while since I had time to work on #PHPCompatibility, but I just wrote a new sniff to detect for one of the #PHP 8.1 deprecations. #MakingThingsBetter


Yet another PHP 8.0 compatibility sniff done. Thanks @elazar for contributing! #php8 #phpcompatibility github.com/PHPCompatibili…


Using Both Composer 1 and Composer 2 — Could be useful if you have legacy projects that require composer 1.x for some reason. colinodell.com/blog/202010/us… #php #composer #phpcompatibility


No results for "#phpcompatibility"

Quão compatível é o seu código PHP e sua loja Magento? Será que ele funciona em todas as versões do PHP? Descubra com um comando. ow.ly/FbwE50BuauE #PHP #Magento #PHPCompatibility #betterCoding

magenteiro's tweet image. Quão compatível é o seu código PHP e sua loja Magento? Será que ele funciona em todas as versões do PHP? 
Descubra com um comando. 
ow.ly/FbwE50BuauE 
#PHP #Magento #PHPCompatibility #betterCoding

Just to be clear - this is not intended as criticism of the Docs team, who do amazing work! Just a returning frustration of PHP moving faster than the docs can keep up and the amount of extra work this causes to maintain #PHPCompatibility. Either way - result:

jrf_nl's tweet image. Just to be clear - this is not intended as criticism of the Docs team, who do amazing work!

Just a returning frustration of PHP moving faster than the docs can keep up and the amount of extra work this causes to maintain #PHPCompatibility.

Either way - result:

Current status: doing my annual round of updating the (always incomplete) #PHP (8.1) Migration Guide based on the research I did to create the PRs for #PHPCompatibility ... *sigh*



Loading...

Something went wrong.


Something went wrong.


United States Trends