Support for PHP 8.0, PHP 8.1 and PHP 8.2

[SimonFrings]

I am currently investing some time into Ratchet and want to test the project against PHP 8.0+. Inspired by #923 by @WyriHaximus, I wanted to try it out myself. Before running the test suite with the PHP 8 versions, I first have to update PHPUnit to the latest version (at least v8, maybe v9 as a first step) and make it work across the current supported PHP versions for this project (PHP 5.4 - PHP 7.4). I did the same thing for ReactPHP a while ago (e.g. reactphp/http#364), so I already know my ways around.

Will keep you posted 👍

[clue]

To add some context: Ratchet already has limited support for PHP 8+ and many people use this in production, but it may report some minor deprecations as mentioned in the linked tickets. I've started looking into this together with @SimonFrings to bring full support for PHP 8+, update the test environment, and fix any warnings. Ratchet could definitely use some love and we're still working on ways to ensure this will be addressed in the future!

If you also want to see this ticket solved, you can upvote or help by sponsoring our development. ❤️ We'll work out a longer-term plan to ensure ongoing development of Ratchet, but this is probably out of scope for this ticket at the moment (see #921?). In the meantime, I'll hide offtopic comments here to allow us to focus and getting things done. 💪

[pgavanuatu]

Hi,
First of all : congrats on the great work on this project.
I need to prepare my code for php8.2 and as you already know... last version of rachet is not working because PHP is becoming a strict language and we need now to declare every Variables.

Is there a timeline for your fixes for php8.2 ?
If it is one month,
I fix it localy with #[AllowDynamicProperties] and wait for your solution

if it is more, I will need to change to something else...

Thanks a lot for your help
Regards
Philippe

[seb303]

Really hope for the new patch to solve the 8.2 depricated issue!

We're using error_reporting(E_ALL ^ E_DEPRECATED); as a workaround where we're using Rachet ... not ideal as it may hide other depreciations which we would want to be aware of.