-
-
Notifications
You must be signed in to change notification settings - Fork 38
Support both evenement 3.0 and 2.0 (and react/stream) #22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
clue
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This currently doesn't have any effect because the Stream version still locks this to an older version. Arguably, this basically means that this is PR is currently untested :-) Does it make sense to update the Stream component as part of this PR? 👍
|
@clue good point, I'll look into that after I fixed the current reason builds fail |
|
I have seen that |
|
@CharlotteDunois you mean this PR WyriHaximus/reactphp-child-process-messenger#13 ? There are some things locally I want to push and finish before merging it, once tagged the only thing in the chain requiring stream 0.4 is this package it self. |
|
@clue done 👍 |
clue
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, thanks for the update, changes LGTM! ![]()
|
Follow up with fixes for failing tests are coming soon as well 👍 |
Événement
.
3.0is nearly fully backwards compatible with2.0andreact/filesystemis fully compatible with all three so why not support it. It packs some neat performance upgrades without any code changes onreact/filesystem's side