-
-
Notifications
You must be signed in to change notification settings - Fork 62
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
Remove BufferedSink #45
Conversation
I'm in favor of both suggestions, also I assume this is for 0.5 then? |
Yeah, this obviously involves a BC break and should target the v0.5 release. |
As long as https://github.com/clue/php-promise-stream-react becomes an official repo 👍 from me |
👍 |
Rebased to remove merge conflicts now that #44 is in. This is currently planned for the future v0.5.0 release. |
Rebased on current master I'd like to get this in for the next release so we can get the v1.0.0 release out and then later look into providing an "official" replacement. In the meantime, https://github.com/clue/php-promise-stream-react works just fine 👍 |
How about we move that to an official repo and package? It looks good to me 👍 . Preferable before merging this/releasing this change. |
I'm not opposed to this, but would rather focus our efforts on the main components first and then look into this? 👍 |
Agreed, mainly wanted to point out that I think it is a bad plan to remove this without official replacement 😄 |
For the reference: The |
This ticket aims to serve as a discussion basis whether this class should actually be part of this repository.
Bridging between Stream-land and Promise-land is arguably out of scope for basic streams. Also, this happens to be the only class that has an "optional dependency" on promises. Full promise support would also involve proper cancellation support, stricter promise version checks and much more…
As an alternative, I would suggest making https://github.com/clue/php-promise-stream-react an official react repo and redirect there.
Builds on top of #44, also solves #24.