PHP 8.4 compatibility#17786
Conversation
01de74a to
8fc71f9
Compare
8fc71f9 to
ccf1810
Compare
ccf1810 to
1977788
Compare
|
I changed the error reporting level in our test suite to not report deprecations. I have done this because I spend too much time on every new PHP version to report/fix the deprecated usages in the vendor libraries. The lint task will still be able to detect most deprecations (see https://github.com/glpi-project/glpi/actions/runs/12029123283/job/33533716142?pr=17786). We may miss some of them, for instance the deprecations triggered when a param has a specific value, but not fixing them ASAP is not an issue. Indeed, they are supposed to have no functional impact and we will anyway be able to detect and fix them when it will be a real issue, i.e. when we will work on a new PHP major version (next will be PHP 9.0 and is still not planned). We may put back the deprecations report in our test suite later, but it requires either to refactor our error handler (for instance to filter the reports depending on their backtrace, and that may be complex), or completely remove our usage of atoum and use the The only library I had to patch is the |
The following dependencies patches were proposed but are not yet all validated or released.
Implicitly marking parameter $param as nullable is deprecatedsabre-io/vobject#673