Skip to content

Conversation

@WyriHaximus
Copy link
Member

@WyriHaximus WyriHaximus commented Feb 28, 2018

Événement 3.0 is nearly fully backwards compatible with 2.0 and react/filesystem is fully compatible with all three so why not support it. It packs some neat performance upgrades without any code changes on react/filesystem's side :shipit: .

Copy link
Member

@clue clue left a 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? 👍

@WyriHaximus
Copy link
Member Author

@clue good point, I'll look into that after I fixed the current reason builds fail

@ghost
Copy link

ghost commented Mar 1, 2018

I have seen that wyrihaximus/react-child-process-messenger locks reactphp/stream down to max. v0.5 by requiring reactphp/child-process v0.4. There seems to be a PR for this, but there hasn't been any recent activity.

@WyriHaximus
Copy link
Member Author

@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.

@WyriHaximus
Copy link
Member Author

@clue done 👍

@WyriHaximus WyriHaximus changed the title Support both evenement 3.0 and 2.0 Support both evenement 3.0 and 2.0 (and react/stream) Mar 23, 2018
Copy link
Member

@clue clue left a 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! :shipit:

@WyriHaximus
Copy link
Member Author

Follow up with fixes for failing tests are coming soon as well 👍

@WyriHaximus WyriHaximus merged commit 01128b7 into reactphp:master Mar 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants