Repository navigation
Replies: 2 comments
|
Yes, definitely planned as part of #1054! 👍 The idea is to make Ratchet compatible with both 0.3.x and 0.4.x simultaneously, supporting both APIs, similar to how we support multiple Symfony versions (see #1095 and #1098). As outlined in #1054, I can't promise an exact date when I'll get to this, but if you’d like to support us reviving Ratchet, please consider sponsoring us – sponsorships really do make a difference. ❤️ |
0 replies
|
Resolved with #1112 finally! 🎉 Ratchet now support v0.4 and v0.3, so it should be fully compatible with Ratchet and other projects relying on newer versions. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I am using this with ratchet/pawl, which supports ratchet/rfc6455 ^0.4.0, but I have to use an older version of pawl since the constructor signature of \Ratchet\RFC6455\Handshake\ClientNegotiator changed between 0.3.x and 0.4.
In ratchet/pawl ^0.4, Ratchet\Client\Connector::__construct() now passes the result of new gPsr\HttpFactory() as the first argument, which is why I have to use 0.3.x. This in turn requires staying on guzzle 7.2 in order to use the now deprecated gPsr\uri_for($url), instead of uriFor. If this package can be updated, I could also update pawl and guzzle.
All reactions