-
Notifications
You must be signed in to change notification settings - Fork 7
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
RxJS support #375
Comments
Do this mean that you confirm your interest in this work, and that I can continue working on apollographql/apollo-client#9331 ? |
@PowerKiKi yes definitely. Thanks for all of your help with this! |
Could you please provide a hint on how to handle |
@PowerKiKi You're welcome to change the public interface of Sorry for the delayed response! |
@jerelmiller could you share the internal status of this work ? is it still something you are considering in the foreseeable future ? or were resources redirected to other developments ? I can see that the previous, aborted, PR is part of the future v4. Is it still accurate ? v2.0.0 was released in 2017 , v3.0.0 in 2020. Does that mean that a v4 may happen in 2024-2025 ? PS: since this issue was created, rxjs became the reference for the new-ish Observable proposal, and Chrome seems to already be working on a prototype implementation. So that probably further solidify rxjs position as the de-facto observable implementation. |
@PowerKiKi we are still in the early stages of v4 planning but we ARE planning on a v4 release this year 🙂. We've talked about it as a team and are all in favor of making the switch to RxJS. I don't have a timeline quite yet, other than to say we are targeting a new major this year. It certainly is time for one 🙂
I did see this! This is super cool and glad we might finally have a built-in primitive. If I remember right, I think I saw that rxjs will over time become more of the "utilities on top of observable" once there is broad browser support? (perhaps a Ben Lesh tweet? Or maybe I'm imagining things 😅). But either way, this is good signal that this change would be a positive one for the library. |
This is a tracking issue for allowing
ApolloClient
andApolloLink
to use alternateObservable
implementations, without bundling a default implementation (currentlyzen-observable-ts
).Thanks to @PowerKiKi for getting this work started twice (and sorry for the long wait):
Related issues:
Other considerations:
The text was updated successfully, but these errors were encountered: